Database Users

[Q]New kernel refuses to boot, how to get a rescue?

OK, this mat have been asked many time, but none of the thread I found applies to my case.
My device is Nexus 7 16Gb Wifi, the internal ROM is stock 4.1.2 (I cannot use 4.2.2 because of a backward compatibility issue for an app I have to use)
The recovery is the latest TWRP 20030227 version, with MultiROM bootloader 4.18. An armhf raring build of Ubuntu is also installed in the internal sdcard and all have worked fine until I tried to flash a alternative kernel.
The new kernel I flashed is the M-kernel mr1.1. I flashed it by booting into recovery and chose to install the M-kernels zip file from there. After I have got a kernel flash successful message I chose to reboot system. Then the weird thing began: at first the device seems to be booting because I saw the usual Google logo and then it turned into the boot animation with a colorful cross in the middle of the screen. But then on nothing seems to follow. The boot animation persists forever. I hve also noticed that during the initial boot it somehow skipped the step of choosing ROMs as usual (because I have Ubunto installed), so I also lost the choice of booting into Ubuntu.
I have to press the power button for more than 10 seconds to power off the device. Then I tried to boot into fastboot mode and recovery mode, both works file, so it still looks not bad. I have kept a copy of my working patched kernel which is kernel_kexec_41-2.zip. Booting into recovery and using the command
adb push kernel_kexec_41-2.zip /sdcard/
I managed to copy this zip into the device. Then, once again, I tried to flash this old kernel by installing it in the recovery. The installation exited with a success. However, when I tried to reboot the device, it is still stuck on the boot animation screen. No choose ROM screen either. So, I am totally lost. Can anybody give some hint on where I was doing wrong and how can I get my device working again without totally reflashing a stock rom and loosing all data I have installed previously? Many thanks.

Any helps please.

Let me update the situation. Tried to wipe cache/Dalvik and reflash the kernels (both the original and the newly downloaded omega3 kernel, both changed nothing -- always stuck in the boot animation. Tried MultiROM->Advanced->Inject curr.boot.sector, the screen allowing to choose rom reappeared and from there Ubuntu boots correctly. However, If the internal ROM is chosen in that screen, the device reboots and stuck in the boot animation screen again.

How about if you make a backup?
Then - no matter what follows - no matter what experiments you do - you can always restore just the /data partition. Or any of the other partitions.
Frankly, you should have done it already, but nothing is stopping you from doing it now.
Backups give you power - and freedom - to experiment with very few risks.
good luck.

Thanks! I didn't realize that I can still make a backup even the system is already broken. Did the backup for the data partition and reflashed the stock rom, it now boots ok. Even though I still lost the desktop configuration and the Ubuntu installation.

instanton said:
Thanks! I didn't realize that I can still make a backup even the system is already broken. Did the backup for the data partition and reflashed the stock rom, it now boots ok. Even though I still lost the desktop configuration and the Ubuntu installation.
Click to expand...
Click to collapse
Had it happened that you still had a bootloop after dirty-flashing /system and/or boot (without doing the custom recovery "factory reset" wipe of /data exclusive of /data/media), a backup can still save your bacon: it can be restored and then manually:
- all system app related /data/data/ and /data/app-lib/ folders removed
- all system app updated .apks in /data/app/ deleted
- wipe dalvik-cache
This leaves all market apps and their data intact while starting from scratch from with the base ROM's system apps. Probably doing that reduces the chances of boot loops.
UID mismatch troubles can still occur if you are coming from a "debloated" ROM and dirty-flashing something like a stock ROM (where there are more system apps than in the prior ROM which generated the /data partition); but I think that TWRP's "fix permissions" should take care of that.
But anyway - backups give you flexibility.

First time flashing ROM and can't install gapps, lesson learned

This post is about the failure to install gapps after flashing ROM and the troubleshooting that ensues.
Posting here, in case somebody might find this helpful. All the best!
I read an article in ibtimes about flashing SuperNexus 4.0 kitkat into Galaxy s3 and I was bored :silly:
I decided to flash SuperNexus 4.0 into my phone, replacing its stock 4.3 Jelly Bean ROM
I rooted the phone first, using Odin 3.0.7 and the CF root that comes with it. It works without hiccups
I downloaded a copy of CWM 6.0.4.6 and flashed it, but it did not work. Failed at Odin. Odin just freezes without failure indication. It took me a couple of hours to finally detach the USB cable and restart the phone out of download mode. It was my first time, of course, I was scared.
I downloaded a copy of CWM 6.0.3.2 and flashed it, it works.
But I decided to download a copy of CWM 6.0.4.5 instead, the one that the ibtimes tutorial links to, and flashed it, it works
However, I can't format /data. I can't mount /data and /system. I can't format Dalvik Cache. I don't have any experience yet, ibtimes seems to indicate that this should not be the behavior, but I moved forward anyway.
I flashed SuperNexus anyway, It works. (flashing SuperNexus is tricky too, I have to edit the updater-script within the zip file to remove asserts. the asserts are causing failure since assert does not match exactly the model number and ROM target)
I tried to flash gapps, but it can't. Reason being that it can't set /system folder during installation setting, probably since CWM can't mount it.
I assumed that the partition is corrupted. I assumed that something messed with the partition since it can't mount it. I assumed that the hiccup while attempting to flash CWM 6.0.4.6 is the culprit
So I mucked around, collecting information on how to do re-partition. However, I ensured that I understand fully about re-partitioning. Since It sounds like it may really brick the phone if I messed it up.
Gathering information about partitioning is a hit miss since the community is filled with reverse engineers. So there are no definitive guide, just guess works.
While following various leads, I tried looking at GPT fdisk since running fdisk shows that /dev/block/mmcblk0 contains only /dev/block/mmcblk0pt1, which leads me to believe that the phone needs gdisk to check the partition (I read this in La Grande partition table reference in xda). I tried to follow this lead, but I have trouble finding gdisk that was compiled for android. When I do find one, I have trouble executing it. I can't seem to be able to chmod it to 764. I dropped this lead.
I flashed Cyanogenmod 10.3, thus reverting back to Jelly Bean 4.3 because SuperNexus 4.0 is not stable yet. Ironic yes? (Removed assert too)
Cyanogenmod works well, in fact, altough I failed to install gapps, the phone is working perfectly. This niggles me into doubting that there is any fault with the partition or the phone.
I tried to sideload gapps. To sideload gapps, I need to run adb alongside CWM in sideload mode. CWM in sideload mode causes the PC to not recognize the phone. It shows the phone as GT-I9305 unknown device.
I failed at finding the driver that could recognize that. Reading off the internet leads me to assume that Windows 8 does not support the USB driver.
I also have this niggling feeling that maybe it is the CWM that is causing the driver problem in sideload mode, since it should be the CWM that communicates with adb.
I re-flashed CWM 6.0.3.2 in hopes that it is more stable.
I now I can connect sideload on adb, but I can't sideload it, because of error, but it looks better since there is actual communication between the phone and abd. Furthermore, device manager identifies the phone as Samsung USB device. I'm feeling optimistic here. Since communicating with adb means the CWM is better than the latest 6.0.4.5. I hope that this CWM can mount /data and /system!
I tried to mount /data and /system on the CWM, lo and behold, it mounted those folders!
I tried to install gapps, the latest one. It soft bricked my phone into boot looping Cyanogenmod, (well at least I believed so since the load takes a longer time than usual) and I did not wait to finish it.
I boot into CWM and format /data /system to reset Cyanogenmod, It works, and loads Cyanogenmod upon reboot
I downloaded the correct gapps version that corresponds to Cyanogenmod 10.3, then booted into CWM and installs the gapps, it works!
I booted into Cyanogenmod and the gapps is finally there!
I opened Google Play, it asks me for my google account. I filled it and all other gapps picks it up, showing contacts, mail and other syncs.
The real culprit? my curiosity? No, CWM 6.0.4.5! Lesson learned: In the world of flashing ROM, the latest might not be the greatest...

Reading you, I could not help but remembering running into the same kind of hurdles a year ago when I rooted and rommed my I9300 for the first time. From my experience, it is quite difficult to brick this phone. I know it, I flashed a kernel instead of a ROM once by mistake.
I never had to tamper with zips, but maybe your S3 is not an international version ?
You should always do a nandroid backup before flashing a new ROM, it can be of great help if something goes wrong.
For the future, I suggest you drop CWM and go to TWRP instead. And as I am running SuperNexus 4.0, and went from CM 10.3 to OmniRom then SuperNexus, I think the stability of these ROMs are comparable. No recurring FCs, no really hampering issues. Probably due to its lack of customizations, I would say SuperNexus is the best of the three in terms of performance.
Anyway, all custom ROMs for Exynos Galaxy S3 usually suffer from issues with graphic drivers (some display elements are badly rendered, I can see it often on wallpapers, as some colors are wrong), and sometimes with the camera. Thanks, Samsung!
The first times flashing can be really stressful, but once you get the hold of it, your phone is running free

Trying to install cyanogenmod to nexus 4, I cannot flash it through TWRP recovery

I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks

I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?

same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J

Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.

It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje

x720 partial unlocked bootloader? [SOLVED]

So I got my 6GB/64GB x720 yesterday. It had Google Play Store already installed (ordered it from HonorBuy) and asked me to install a 7MB OTA, so it seems it had a recent version of EUI on it. My idea was to put LineageOS 14.1 on it or if it wasn't stable enough for me, at least a debloated and rooted stock. So searched XDA and followed this HowTo. No Errors, flashboot oem device-info said, bootloader unlocked, perfekt. Installed TWRP, downloaded recent LineageOS and followed the guides to flash (wipe, ...). Unfortunately flashing never finished, I always had a full progress-bar and it stayed there without doing anything (ok, the device got hot). Thinking of a broken download, I redownloaded the ROM but same problem. So I started downloading other ROMs from XDA: Resurection Remix and OmniROM. Flashing-process went thru, but couldn't flash gapps and ROMs didn't boot at all. I was always only getting to the LeEco-Bootlogo with the chinese writings. So next thought was, maybe for some reason I can't install Lineage-based ROMs, let's figure out later and get a debloated stock ROM. So I downloaded MAURO V2.2_Free and gave it another try. Looked more promising, as the bootlogo was a little different, no more chinese writing but english. Unfortunately this was all I could see of MAURO as I only got a bootloop... so again reflashed MAURO and this time a single line in TWRP-output came to my eye "boot.img could not be written". I checked flashboot oem device-info after every flash and it always told me, bootloader is unlocked, but there seems to be something else that I'm missing that obviously still keeps the bootloader locked. I wiped the phone several times, even sdcard... nothing helped. The only method that worked for me to get a working rom running was by this guide, manualy flashing every bit of stock ROM with flashboot. With MAURO-ROM, I also tried to flash boot.img manually with flashboot, but that didn't work, either.
Anyone of you experienced the same? What am I missing? Or is this some new protection implemented by LeEco for the most recent devices? Any help really appreciated!
regards
CDFS

I have the same phone from Honorbuy, I flashed twrp using the tool by Mauronofrio and from the twrp wiped all and flashed the custom rom, all went ok, no errors at all! Glad to see you have solved anyway!

Thanks for the answer... no, it's not solved for me... still a lot of bloat on the phone I can't get rid of. Do you have a link for the tool you mentioned? Could be worth a try...

Hi! I've used this tool installing it on a Windows 7 64 system:
https://forum.xda-developers.com/le-pro3/development/tool-tool-one-mauronofrio-t3580611
Then turned ON the (original LeEco stock rom) usb debug option by the rom's developer options, then downloaded the LineageOS 14.1 by Team Superluminal in the phone's internal SD (the only SD it have!) + Arm64 nano Gapps, then with the tool gave a reboot in sideload mode. Then flashed the twrp recovery by the tool, restarted in recovery mode then executed a backup of ALL the "backupable" stuff (all the original rom and data and efs), then in wipe/advanced options I wiped dalvik, system, cache, data. Then in Advanced/file manager I wiped all the SD files with a dot ( . ) at the beginning of their names, then flashed the custom rom + gapps, reboot system, wait some minutes, done!

No luck with this tool, it doesn't even find my device. Any other ideas? I've read something for the x727, where they had to flash a 19s bootloader first, but I don't want to fiddle with flashing files that are not 100% meant for the x720...
CDFS

Solved! As I could install TWRP I just went the next step and installed SuperSU (rooted the phone) in order to at least debloat stock rom. During the installation of SuperSU I saw, that SuperSU obviously patches somehow the bootloader. After checking that SuperSU worked in the ROM, I was curious if this could be the missing part I was searching for. I tried to install a LineageOS-based ROM and BINGO! it just went straight through! From my previous phones I was used to just install TWRP, wipe anything and flash desired ROM. This seems to be different on this device... so the proper procedure to be able to flash any ROMs is: Install TWRP, root stock ROM, reboot so SuperSU is fully functional, then go back into TWRP, wipe, flash what you want.
CDFS

I hate to say it, but it's still not solved. After testing Resurrection Remix, I wanted to test turbos ROMs, so went to TWRP, wiped and flashed... and got the same behaviour as before, ROM not booting. Also installing SuperSU via TWRP again didn't help, so brought back the phone to stock 023S manualy with the guide by Presterin, installed TWRP again and also SuperSU. No Errors, but flashing a different ROM didn't worked. So for now I'm back to stock, rooted it and tried to debloat it by myself. The only difference between the successful flashing and the failed was the stock version: I had the 026S-update when I rooted the phone and successfuly could flash another ROM. My guess would be that LeEco changed something in the bootloader, but I have no chance to verify this. Anyone from the devs maybe who could look into this? If you need dumos, logs or anything like that, I would be happy to help.
CDFS

This seems unrelated to bootloader.
Anyway:
1. Make sure you got the latest firmware, if not sure:
1.1. Download latest OFFICIAL ROM
1.2. Rename the rom to a 'update.zip' and place it on phone's root directory.
1.3. Reboot to fastboot and flash STOCK RECOVERY
1.4. Reboot to recovery and flash, also check wipe data.
DO NOT FLASH STOCK ROM WITH TWRP! THIS WILL NOT WORK!
That's it, you should have the latest firmware now.
After booting to stock rom, reboot a few times is recommended.
2. Download latest OFFICIAL TWRP
2.1. Flash TWRP with fastboot.
2.2. Reboot to TWRP.
2.3. Download any custom rom of your choice.
2.4. Wipe.
2.5 Flash.
Done.

You can try to flash a stock, old rom using the "Qfil/FlashOne" way as suggested by Tryzex (read his thread and other related threads), then once you have got a stable, full working phone, you can (hopefully!) wait for a LeEco OTA automatic update that can "repair" the file system/partition structure (also bootloader I hope!).
Btw, to debloat it isn't necessary to root the phone, you can keep the phone unrooted & debloated using the file manager embedded in twrp recovery to delete/replace any file/app you want. I'm sorry I can't help you better, cheers and... good luck!
PS
I see now the post from Voron00, it's a good hint!

@voron00 thx for the steps described. I'm using the most recent, official TWRP (3.1.1). Latest Official Stock seems to be 023S on their site, even though there is a 026S update. However, I did this 026S-update and rooted again, but was to cusious if flashing would work now... so I tried flashing turbos MIUI... guess what? It worked. So for whatever reason I seem to have trouble when flashing from a 023S, but no problems when flashing from 026S. I don't quite understand why you think that my problem is not related to the bootloader? As mentioned in the OP, I could see in the logs that while flashing, some roms had thrown errors regarding writing the bootpartition.
CDFS

Seems as I found the culprit, somehow. At least I could flash two other ROMs without any problems. Obviously I mixed and partly missinterpreted some steps found in different threads and howtos. I had "rm -rf for formating" ticked all the time in TWRP. My flashing procedure is now as follows:
1. in TWRP settings check that "rm -rf instead of format" is NOT ticked
2. wipe Cache, System and Data
3. repair filesystem for Cache, System and Data and check that no errors occur
4. in TWRP settings tick "rm -rf instead of format"
5. flash ROM
6. wipe Dalvik
CDFS

"rm -rf" clears all the files and directories without formatting the partition. If your partition is damaged you need a real format to obtain a reliable partition (if the "disk" isn't faulty). Perhaps in your case a real format was required to solve the problem! I always used the real format and assumed other users even so. I see you finally solved the problem!

mi 9t (global i think)tried installing custom rom wiped system partition now only fastboot works. now what?

hi!
i was in the middle of installing a new custom rom on my mi 9t/k20 (i think global/eu which was running miui 11 previously) and i wiped the partitions as follow: dalvik, cache, data and system
i believe that the only thing concerning on that list would be the system partition being wiped.
currently my device is stuck in fastboot mode (i can still send commands to it and do stuff) but i dont ave a recovery ...
so i have an idea of a plan which is:
1. flash twrp
2. wipe the 4 partitions again
3. reinstall the stock rom
4. update the phone to miui 12
5. wipe the partitions again
6. install custom rom twrp and magisk
is there anything i should know before i do this?
also some links to working twrp version would be nice (lost the original version that i had installed)

The_Wrench said:
hi!
i was in the middle of installing a new custom rom on my mi 9t/k20 (i think global/eu which was running miui 11 previously) and i wiped the partitions as follow: dalvik, cache, data and system
i believe that the only thing concerning on that list would be the system partition being wiped.
currently my device is stuck in fastboot mode (i can still send commands to it and do stuff) but i dont ave a recovery ...
so i have an idea of a plan which is:
1. flash twrp
2. wipe the 4 partitions again
3. reinstall the stock rom
4. update the phone to miui 12
5. wipe the partitions again
6. install custom rom twrp and magisk
is there anything i should know before i do this?
also some links to working twrp version would be nice (lost the original version that i had installed)
Click to expand...
Click to collapse
-When installing custom ROMs (changing ROM types), you have to F O R M A T Data (not Wipe) - it's totally different (stronger) and can be found elswhere in guides
-Wiping System is totally bogus: new ROM will nevertheless replace the System (no matter did you wipe it or not)
However, if you are changing from MIUI CN to Global or so - then totally different procedure applies.
It's not enough to flash the new System but also to change the Vendor.
For that case google for and read about using MIUI Flash

zgfg said:
-When installing custom ROMs (changing ROM types), you have to F O R M A T Data (not Wipe) - it's totally different (stronger) and can be found elswhere in guides
-Wiping System is totally bogus: new ROM will nevertheless replace the System
Click to expand...
Click to collapse
ok cool thx but do you think that i can install twrp rn without a system?
or is that not gonna work? cause idk how else id install a new rom

The_Wrench said:
ok cool thx but do you think that i can install twrp rn without a system?
or is that not gonna work? cause idk how else id install a new rom
Click to expand...
Click to collapse
I don't really know what else you might have (possibly) mesed up. I have just updated the previous post so please read again the part about MIUI Flash
(If you were not changing from CN/EEA/Russia to Global or so but only installing a custom/AOSP ROM, then if you wiped Data instead of formatting - you would be bootlooping niw to TWRP and you would simply need to Format Data to fix it
But if you were really changing from eg CN to Global by just flashing System - that is TOTALLY WRONG way, why didn't you research how to do it properly by MIUI Flash?
In that case you could still try MIUI Flash, if not working you would need somebody with paid EDL support (I cannot help you for that)
Sorry, good night now

zgfg said:
I don't really know what else you might have (possibly) mesed. I have just updated the previous post so please read again the part about MIUU Flash
(If you did not change from CN/EEA/Russia to Global but only installing a custom ROM, then if you wiped Data instead of formatting - then you would be bootlooping to TWRP and you would simply need now to Firmat Data
But if you were really changing from eg CN to Global by just flashing System - that is TOTALLY WRONG way, why didn't you research how to do it by MIUI Flash?
In that case you could try MIUI Flash, if not you would need somebody with EDL (I cannot help you for that)
Sorry, good night now
Click to expand...
Click to collapse
no i havent changed the region form the phone ... however my currently big problem is that im stuck in fastboot mode and i cannot enter recovery i could try and reflash recovery via fastboot but im not sure if that would break it even more. and since there is no OS on the devices either i cant use adb either. my last hope rn is fastboot and idk what to do rn to fix all this back to factory OS state or a similiar state

The_Wrench said:
no i havent changed the region form the phone ... however my currently big problem is that im stuck in fastboot mode and i cannot enter recovery i could try and reflash recovery via fastboot but im not sure if that would break it even more. and since there is no OS on the devices either i cant use adb either. my last hope rn is fastboot and idk what to do rn to fix all this back to factory OS state or a similiar state
Click to expand...
Click to collapse
As said, something more terribly messed up. Please google and research about using MIUI Flash (TG, I didn't need to use hence cannot help, but there are GOOD guides on the Net)
Good luck and good night

i found this and did what he did https://forum.xda-developers.com/t/xiaomi-mi-9t-stuck-in-fastboot.4255741/
helped a lot now imma retry