I'm following along this video. https://www.youtube.com/watch?v=GNgg1_JZrSE
I downloaded the files, opened and ran odin, that went well, I copied the SuperSU file to the root of my tablet storage and powered off. Unplugged the USB and booted into recovery using power and volume up. But his screen looks custom, while mine looks like the default screen with a big "No command" message, with options like reboot system now, apply update from ADB/external storage, etc. How do I get the custom display to show up like his does at 9:19 in the video. Thats where Im stuck at right now
Related
Hello. I'm stuck in Android System Recovery <3e> and i need your help, thank you in advance.
I'm afraid to brick the phone and i'd really appreciate some fast help! I'm affraid the phone could run out of battery even if plugged in!
I downloaded Samsung Galaxy NoteII Toolkit V4.1.0
I installed the drivers
I started to root my phone, I chose the fifth option
"Will either push the selected root file to your Internal Storage, guide you through flashing Custom Recovery via Odin. When the device reboots it will bot to recovery so root files can be flashed + rename the recovery restore files. Or install the zip file via adb sideload after recovery boots. plus busybox will also be installed"
Click to expand...
Click to collapse
I went trough Odin, and then when the phone was detected I chose cwm and it rebooted again, it went in Android System Recovery <3>
I can read this
Android System recovery <3e>
Volume up down to move highlight
power button to select
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset.
wipe cache partition
Apply update from cache
#MANUAL MODE#
--Appling Multi-CSC...
Applied the CSC-Code: DBT
Successfully applied multi CSC.
Click to expand...
Click to collapse
The toolkit told me to press any button when i was in sideload mode. So i pressed and it said "error: closed" then i sayed press any button when file installed ready to reboot (something like that). I tried and i pressed a random key and it said "error: closed" and went back to main menu and i'm still in Android system recovery <3e>
Now, i'm still plugged to the computer. I'd would like to start all over. What should i do? Reboot system now? unplug the phone? Take the battery out? I already tried power + volume up combo. It reboot and goes back to where i was.
I'm afraid to brick the phone and i'd really appreciate some fast help! I'm affraid the phone could run out of battery even if plugged in!
Edit: I took a shot and chose "reboot system now". Everything seems to work fine but Root checkers says i'm not rooted. I would like to know if i can start again without worrying about what happen?
greenortor said:
Hello. I'm stuck in Android System Recovery <3e> and i need your help, thank you in advance.
I'm afraid to brick the phone and i'd really appreciate some fast help! I'm affraid the phone could run out of battery even if plugged in!
I downloaded Samsung Galaxy NoteII Toolkit V4.1.0
I installed the drivers
I started to root my phone, I chose the fifth option
I went trough Odin, and then when the phone was detected I chose cwm and it rebooted again, it went in Android System Recovery <3>
I can read this
The toolkit told me to press any button when i was in sideload mode. So i pressed and it said "error: closed" then i sayed press any button when file installed ready to reboot (something like that). I tried and i pressed a random key and it said "error: closed" and went back to main menu and i'm still in Android system recovery <3e>
Now, i'm still plugged to the computer. I'd would like to start all over. What should i do? Reboot system now? unplug the phone? Take the battery out? I already tried power + volume up combo. It reboot and goes back to where i was.
I'm afraid to brick the phone and i'd really appreciate some fast help! I'm affraid the phone could run out of battery even if plugged in!
Edit: I took a shot and chose "reboot system now". Everything seems to work fine but Root checkers says i'm not rooted. I would like to know if i can start again without worrying about what happen?
Click to expand...
Click to collapse
use this :good:
http://forum.xda-developers.com/showthread.php?t=2445480
pijiey2 said:
use this :good:
http://forum.xda-developers.com/showthread.php?t=2445480
Click to expand...
Click to collapse
Thank you very much but i still have a slight problem. How do i know what has been modified? for example: has CWM been installed on my Note?
Thanks in advance.
If u follow the step in aroma, u should have cwm
Hello,
I hope someone can help me. I'm not completely ignorant when it comes to rooting and flashing custom roms, but it's been a while since the last time I did (last time was my Samsung Galaxy S2). Today I decided I was going to root my N5110 Note 8 and install a 4.4.2 rom on it.
I decided I was going to install the Omni Rom linked here: http://forum.xda-developers.com/showthread.php?t=2569099
I apologize in advance for the long descriptions below.
Here are the steps and issues in the order that it happened:
1) Flashed CF-Auto-Root-konawifi-konawifixx-gtn5110 using Odin (Auto Reboot, F. Reset Time)
2) Downloaded Rom Manager App, and booted into Recovery from there.
3) Using CWM Recovery, I followed instructions as described on the Omni link and did a Wipe/Factory Reset
4) Using CWM Recovery, I selected to install zip from SDCard, and selected the omni-4.4.2-20140102-n5110-HOMEMADE.zip
5) After a few seconds, I got an error 7, and the installation aborted.
6) Tried to reboot back to the system, but of course now that everything is wiped, it just loops back to recovery.
7) I tried installing the zip again, same error. I checked the thread and someone mentioned the same error. OP mentioned using TWRP, so I went back into Download mode and flashed TWRP via Odin
8) After reboot, it went into TWRP. Tried installing zip again, same error. I decided I'll pick up another rom to try first. So, I took out my microSD card so that I can load the ROM over to it.
9) Booted back into TWRP - it no longer sees my SD card. Tried to power down from recovery menus in hopes to get it to see the sd card. No luck
10) I'm desperate now--I am trying to force it off by holding down the power button. It reboots back into recovery. I even try to get it back to download mode so I can flash CWM back on, in hopes that it will let me retry. But now it just shows the battery screen (like when you're charging it while powered off) at empty. I unplug the USB cable, the screen turns off.
11) I try to power it back on without the USB cable plugged in, nothing happens.
12) I plug the USB power back in, and it looks like it's booting up. It goes to the Samsung Note 8.0 N5110 screen and just flickers. The flickering increases in speed over time.
13) I force it back into Download mode, and try to run the CF Auto-Root again (like I said I'm desperate now).
14) After Odin reboots the device, it goes into the battery screen and is doing the weird flickering thing again.
I'm currently attempting to download XXCMH3_stock-rooted-official.zip in hopes to flash via Odin, but the d/l keeps timing out before the whole thing can be transferred.
Someone, please help! What am I doing wrong?
bbqnjl said:
Hello,
I hope someone can help me. I'm not completely ignorant when it comes to rooting and flashing custom roms, but it's been a while since the last time I did (last time was my Samsung Galaxy S2). Today I decided I was going to root my N5110 Note 8 and install a 4.4.2 rom on it.
I decided I was going to install the Omni Rom linked here: http://forum.xda-developers.com/showthread.php?t=2569099
I apologize in advance for the long descriptions below.
Here are the steps and issues in the order that it happened:
1) Flashed CF-Auto-Root-konawifi-konawifixx-gtn5110 using Odin (Auto Reboot, F. Reset Time)
2) Downloaded Rom Manager App, and booted into Recovery from there.
3) Using CWM Recovery, I followed instructions as described on the Omni link and did a Wipe/Factory Reset
4) Using CWM Recovery, I selected to install zip from SDCard, and selected the omni-4.4.2-20140102-n5110-HOMEMADE.zip
5) After a few seconds, I got an error 7, and the installation aborted.
6) Tried to reboot back to the system, but of course now that everything is wiped, it just loops back to recovery.
7) I tried installing the zip again, same error. I checked the thread and someone mentioned the same error. OP mentioned using TWRP, so I went back into Download mode and flashed TWRP via Odin
8) After reboot, it went into TWRP. Tried installing zip again, same error. I decided I'll pick up another rom to try first. So, I took out my microSD card so that I can load the ROM over to it.
9) Booted back into TWRP - it no longer sees my SD card. Tried to power down from recovery menus in hopes to get it to see the sd card. No luck
10) I'm desperate now--I am trying to force it off by holding down the power button. It reboots back into recovery. I even try to get it back to download mode so I can flash CWM back on, in hopes that it will let me retry. But now it just shows the battery screen (like when you're charging it while powered off) at empty. I unplug the USB cable, the screen turns off.
11) I try to power it back on without the USB cable plugged in, nothing happens.
12) I plug the USB power back in, and it looks like it's booting up. It goes to the Samsung Note 8.0 N5110 screen and just flickers. The flickering increases in speed over time.
13) I force it back into Download mode, and try to run the CF Auto-Root again (like I said I'm desperate now).
14) After Odin reboots the device, it goes into the battery screen and is doing the weird flickering thing again.
I'm currently attempting to download XXCMH3_stock-rooted-official.zip in hopes to flash via Odin, but the d/l keeps timing out before the whole thing can be transferred.
Someone, please help! What am I doing wrong?
Click to expand...
Click to collapse
Hi, just so you know... you do not need to root a stock ROM to flash a custom ROM... I am surprised that you think that is necessary
Did you ever set USB debugging to enabled?
Also what Odin do you have?
Turn off note, remove SD, and see if you can start in Stock download mode.
Flash with Odin 3.07... repeat flash with Odin 3.07 and use N5110UEFMI1_N5110XARFMI1_HOME.tar.md5 from http://samsungis.com/
Here is a copy of a reply on a thread it may help if you cannot perform the simple task of reflashing stock ROM from my small list of steps.
Harjan112 said:
Have you tried to flash with Re-Partition checked in Odin 3.07? It looks like your partions are messed up, if it was me I would just give it a try "flashing with re-partition checked" seeing as though its not working anyway.
If that don't work see if you can get a PIT file somewhere, I did read someone put up a link for a PIT file here http://forum.xda-developers.com/showthread.php?t=2544451 although I am NOT 100% sure if this is for the GT-N5110 but read thru it and if you feel adventurous give that PIT file a try.
And here is a link http://storagecow.eu/index.php?dir=Xda/Galaxy+Note+8/XXCMG2/ that someone put up with a leaked firmware and the PIT file and CODE file for the N5110 you can give that a try also.
- Unzip the file
- Open Odin 3.07 (already included in the firmware package)
- Restart phone in download mode
(Press and hold Home + Power + Volume down buttons)
- Connect phone and wait until you get a blue sign in Odin
- Add CODE_N5110XXCMG2_1031850_REV01_user_low_ship.tar to CODE
- Add CSC_OXA_N5110OXACMG2_1031850_REV01_user_mid_noship .tar to CSC
- Add kona_wifi.pit to PIT
- Make sure re-partition is ticked
- Start flash, sit back and wait a few minutes.
- If you encounter any issues with the firmware (Any FC, Bootloop etc)
- Boot into recovery mode (Home+ Power + Volume Up)
- Choose to wipe/factory reset.
(THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!
Click to expand...
Click to collapse
GT-N5110 & GT-N5120 - 64GB 633x on board, Status Official on SafeRooted OEM ROMs with Wanam Xposed and RootCloak. The only way to fly 8+ hours!
This badboy don't play with Play & Triangle away!
In TWRP v2.6.3.0 look under mount and see if Micro Sdcard has an "x" if there is no "x" check this and go back to the screen where is says reboot ... reboot recovery from there, once rebooted in recovery go to install and in the top (if you are on v2.6.3.0) you should see storage, tap that and you should have a choice from internal storage and Micro SDcard, if you see Micro SDcard there you should select that and hit ok.
Hoping this helps.
Sent from my SPH-L900 using xda premium
My apologies. I didn't see any of the replies since my email subscription went to my spam folder.
Thank you for those of you who took the time to try and help me.
I know I didn't have to flash stock, but it was more of me being desperate and just trying to put ANY rom on to get it to turn on.
By some weird luck, I had got my tablet working the next day. Basically, in defeat, I just let it sit on the charger overnight thinking a full tank of gas would help it. The next morning, I seriously just pressed all the button combinations and managed to get it to go into recovery and see my SD. I tried yet again to install the Omni Rom again but no dice. It gave me an error again.
So I tried to install a rom again, this time the PAC-rom.
It worked!
Tablet is functional again!
So thank all of you and the electronics god for the miracle!
Have a great weekend you fine folks!
IS the android recovery menu stored in the bootloader?
Does the bootloader corresponds to the file boot.img on SP FLASH TOOL?
I have an alcatel 7047 xpop c9 (with MT6582M processor) . It power on and automatically goes to android recovery menu and there is no way to let it exit from this mode or to power off because the battery is not removable.
It seems that the problem appeared during an upgrade, because the battery discharged during the process.
Today i tried to use SP FLASH TOOL version 5 in order to write the flash, included preloader, boot, recovery etc., by using a backup for this phone found on internet. After flashing everything i tried to reboot the phone but each time the same menu is shown.
Question: does the boot.img file overwrites the bootloader? How could I understand what is the problem? Could I enable some print or log, even remote logging, in order to better understand what is going wrong?
Yesterday i also tried the upgrade tool from alcatel website (it reloads all the original files but the result is the same).
EDIT: i was able to open the case, remove the battery and replug it, but the problem is still the same: Reconnecting the battery and powering the phone, it automatically goes in the recovery menu.
Wow
Wow, no reply. Is it there someone hereeeeeeeee?
gaucho1978 said:
IS the android recovery menu stored in the bootloader?
Does the bootloader corresponds to the file boot.img on SP FLASH TOOL?
I have an alcatel 7047 xpop c9 (with MT6582M processor) . It power on and automatically goes to android recovery menu and there is no way to let it exit from this mode or to power off because the battery is not removable.
It seems that the problem appeared during an upgrade, because the battery discharged during the process.
Today i tried to use SP FLASH TOOL version 5 in order to write the flash, included preloader, boot, recovery etc., by using a backup for this phone found on internet. After flashing everything i tried to reboot the phone but each time the same menu is shown.
Question: does the boot.img file overwrites the bootloader? How could I understand what is the problem? Could I enable some print or log, even remote logging, in order to better understand what is going wrong?
Yesterday i also tried the upgrade tool from alcatel website (it reloads all the original files but the result is the same).
EDIT: i was able to open the case, remove the battery and replug it, but the problem is still the same: Reconnecting the battery and powering the phone, it automatically goes in the recovery menu.
Click to expand...
Click to collapse
Just discovered your post. Have you solved the issue?
First of all, the recovery image is not stored in the bootloader...whatever you meant by that. It is stored in the recovery partition. The boot.img is NOT the bootloader. It is the kernel. And it is stored in the boot partition. Those questions simply sound like you are trying to figure out why your phone is booting into recovery. Even after you have restored the STOCK ROM using Alcatel's Mobile Upgrade S.
My first thought was that you have no system image or that your custpack partition is corrupted. But those issues would lead to a boot loop or you would just hang on the boot logo and not move forward. Plus you restored the stock ROM. So that's really strange that you're booting only into recovery each time.
However what is more likely is that you are not starting your phone correctly. I once had a lady with the exact same issue. Her phone developed this strange problem where it would only boot into recovery. Her phone was completely stock. She never did anything with her phone except use it like a non-techie would use their phone. She didn't even know what recovery meant. All she knew was this strange menu always appeared when she started her phone.
BUT, when I booted her phone...guess what? It booted up just fine! But with her, her phone would always boot into recovery. You know why? I watched her boot her phone. She had developed a new habit every time she started her phone of inadvertently applying pressure on the Volume UP button while she was turning on her phone...because it was on the opposite side of the phone from the power button.
It's really weird that the problem persists even after you flashed back to stock. If that's the case, my only other guess is that your motherboard is damaged, or perhaps it's not you who is holding down the vol+ button...maybe it's just stuck.
So I was updating six rom and phone went into continuous boot. So went into recovery and wiped all but internal memory and reinstalled. Same boot problem. Went into fast boot and pushed another over as well as a vendor image. Tried installing the new rom, beans gaps, super su and same result. I've left the phone for over 20 mins with no result but the boot screen.
I'm having a similar problem.
My status- Unlocked bootloader, twrp accessible, devices not getting detected in fastboot mode by the pc, rooted, restoring using the backup results in a bootloop, correct drivers installed on the pc, superSU and full backup in the mobile.
i cant transfer files since device not getting detected.
my timeline- i followed every instruction on https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 and everything went successful, but when it rebooted to the 'Welcome' page (the page which comes when u open mobile for the first time) i restarted my nexus 5x 32gb to recovery mode and then the every boot procedure doesn't complete for several minutes(doesn't go ahead the ball animation)
note: everything that I've flashed was from my SD card; I had the files on /sdcard1/Download
note 2: since my device's bootloader is unlocked, I have to press the power button after turning on the device, so that the "bootloader unlocked" warning goes away
I've managed to install TWRP (I followed this guide, "How to Install twrp Recovery on Samsung SM-T295" part, I modified a bit the steps, i had to go into download mode again after flashing TWRP_3.4.0.1+vbmeta_T295.tar and flash aboot_vk_T295XXS3ATB4.tar) and then LineageOS 17.1 (from a GSI I found on this post, to flash I followed this guide) on a Samsung Galaxy Tab A 8.0 (2019) (SM-T295). Then I rooted it after installing LOS (from this guide, "How to Root Samsung SM-T295" part, I didn't make a backup due to errors, and multidisabler-samsung-2.6.zip failed to flash). Magisk had to update after, so I did that. Until then, no errors, until I downloaded BitGApps (I followed this guide, I downloaded the ARM64 version for Android 10 directly from my device). My TWRP had some problems flashing, because I couldn't access the Internal Storage from there (for some reason, /sdcard directory shows only folders on Install (and files, in the file manager) with random numbers and letters names like MAKVjaaw24Ajg35waD (not an actual folder or file, just an example), and I couldn't find the files to flash, which is why i had to flash everything from my SD card), so I rebooted to system from TWRP, and tried to copy the BitGApps file to my SD card so I could flash. I think I was about to copy the file (or I had just selected the copy option but hadn't found the directory to copy the file to, which was /sdcard1/Download), and suddenly, my device just powered off. I thought "oh it's just a bug, I'll power it on again and it'll be fine", but something strange happened when I powered it on; Now, every time I turn it on with the power button, I have to hold it less time for it to boot for some reason. That's weird. When android started and I could use the device, I tried to copy BitGApps to my SD card again, but my tablet powered off again and the same happens every time now. When i boot into safe mode, this doesn't happen, so I suspect it happens because of an app I installed, and now that I think about it while writing, I think it's probably Magisk Manager (I made it so that Magisk allows any superuser request, which is why I think Magisk has to do). I have the apps Phone Guardian (I always install it because I love it), Magisk Manager and the Official TWRP app.
Also something weird I noticed; Ever since the first time it bugged for me, whenever I boot into TWRP and then power off from the reboot menu, next boot is TWRP even if I don't do the button combo to boot into recovery (for my SM-T295 it's hold power + hold volume up at the same time when the device is off, then when it powers on, release all the keys and press power when promted to make the "bootloader unlocked" warning go away if necessary).
Does anyone have any ideas on why this is happening? Am I right on my guess that Magisk is faulty? Do I need to uninstall it and unroot if that's the case? Thank you all in advance.
Update: it was Magisk, but not the option I said, maybe a module?
Update: I got it now.
Jaqueek said:
Update: it was Magisk, but not the option I said, maybe a module?
Click to expand...
Click to collapse
No, I was wrong. I figured it out. It bugs after I update to Magisk 21.3 from 20.4. The manager is not a problem. Also,...
Jaqueek said:
Now, every time I turn it on with the power button, I have to hold it less time for it to boot for some reason. That's weird.
Click to expand...
Click to collapse
... It is weird indeed, but not important, it's not annoying and useful if I'm in a hurry or smth so I can't complain. Also, after I uninstalled Magisk that didn't dissapear. Anyways, I just don't care about that anymore.
Also, I managed to flash GApps pico, it was a little hard.
One last thing, when I said that my TWRP saw gibberish when trying to access /sdcard1,
it appeared to not be only TWRP. Stock File Manager saw those weird names too, after I wiped the Internal Storage partition. I just fixed content in TWRP and wiped Int. Storage again, it's fine now. I still haven't checked TWRP though. (just checked, yeah it looks the same still but any file manager is fine)
So, what is causing my device to turn off when I update to Magisk 21.3?
Edit: It also happens when I uninstall the original and install the new one.
How did you get the Treble GSI working on this device?
Mine just bootloops on the bootloader, even after doing your steps...