so the story goes like that.
few days ago (before ICS officialy came from asus) i've tried just for fun Paul's ICS port. i really dont see myself as a noob, so please treat my question as it is.
at first i've tried to flash it from cwm without wiping and stuff- got stuck at boot.
so i did i full wipe with "Android revolution super wipe".
and flashed ics port again- now with success.
after couple of days decided to go back to HC Revolver. so just went again to CWM and full wiped again, and flashed revolver 3.11.
then i started to get the bad news. it seems nothing can be flashed anymore from the recovery. when i flash a rom it finishing it too fast and when i reboot it just bootlooping on the splash screen. tried everything, including removing the cwm recovery and installing it again.
the one and only thing that worked is nvflashing a prime rom. but it still didnt fix the recovery problem.
i tried to flash also back HC kernel with no luck.
what did go wrong?!
please help me
num1gever said:
so the story goes like that.
few days ago (before ICS officialy came from asus) i've tried just for fun Paul's ICS port. i really dont see myself as a noob, so please treat my question as it is.
at first i've tried to flash it from cwm without wiping and stuff- got stuck at boot.
so i did i full wipe with "Android revolution super wipe".
and flashed ics port again- now with success.
after couple of days decided to go back to HC Revolver. so just went again to CWM and full wiped again, and flashed revolver 3.11.
then i started to get the bad news. it seems nothing can be flashed anymore from the recovery. when i flash a rom it finishing it too fast and when i reboot it just bootlooping on the splash screen. tried everything, including removing the cwm recovery and installing it again.
the one and only thing that worked is nvflashing a prime rom. but it still didnt fix the recovery problem.
i tried to flash also back HC kernel with no luck.
what did go wrong?!
please help me
Click to expand...
Click to collapse
You need to flash the stock kernel again, Paul's ICS kernel is still there, and that won't work. CWM does not flash the kernel when flashing a ROM unless the kernel is included with the ROM (like Paul's). Download Roach2010's kernel and CWM flash it, then reboot and see if that fixes it. Then, if you want to go to stock, use revolver parts to download the stock Asus kernel and return to stock.
Try hereee
http://forum.xda-developers.com/showthread.php?t=1513698
And then here
http://www.tabletroms.com/forums/tra...ing-tools.html
Related
Ok, so I have been running a nice custom ROM of ICS on my phone, I then tried the updated version for a couple of days, but deceided to revert back to my previous back up. Did the back up through CWM manager, but from here, it failed to boot and went to the black "Samsung Galaxy note" screen.
I then went in to recovery, did a full wipe, and then just tried to re install my custom ICS ROM. It only got as far as flashing the modem, and then hangs, I tried this a few times, and with a few different roms. Pre ICS roms, and a stock KK9 rom just failed instantly.
I then put the phone in to download mode, and hooked it up to the PC to do a flash through ODIN.
I selected a stock KK9 rom, but this failed.
I now cant get to recovery, and I dont have the black "samsung galaxy note" screen, it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
I then try to do this, but Kies wont connect to the phone.
I am at a loss, please help
I'm really sorry about your trouble..I can't really help with your current issue but I can tell you what probably happened.
You probably tried to restore a gingerbread backup while using the ICS recovery. You just can't do that.
When you want to flash a gingerbread rom or gingerbread backup coming from a ICS rom you must ALWAYS flash a gingerbread kernel first. After that simply reboot recovery in advanced section and then restore gingerbread from there.
That way you know next time..Hope you get it fixed.
Sent from my GT-N7000
dannstarr said:
Ok, so I have been running a nice custom ROM of ICS on my phone, I then tried the updated version for a couple of days, but deceided to revert back to my previous back up. Did the back up through CWM manager, but from here, it failed to boot and went to the black "Samsung Galaxy note" screen.
I then went in to recovery, did a full wipe, and then just tried to re install my custom ICS ROM. It only got as far as flashing the modem, and then hangs, I tried this a few times, and with a few different roms. Pre ICS roms, and a stock KK9 rom just failed instantly.
I then put the phone in to download mode, and hooked it up to the PC to do a flash through ODIN.
I selected a stock KK9 rom, but this failed.
I now cant get to recovery, and I dont have the black "samsung galaxy note" screen, it just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
I then try to do this, but Kies wont connect to the phone.
I am at a loss, please help
Click to expand...
Click to collapse
I assume the stock KK9 rom is from your region? Same thing happened to me because I stupidly flashed a rom that wasn't from my region (I have an unlocked phone from India). Hopefully that's what happened because it was an easy fix for me. Good luck!
Which custom ics rom did you have and which recovery?
Sent from my GT-N7000 using Tapatalk
When flashing between ICS ROMs I often flash the Abyss kernel first and then flash a new ROM from it's recovery. I think the issue is that your ICS ROM was not fully rooted. Try to flash Abyss kernel and the wipe and flash your next ROM.
csasek said:
When flashing between ICS ROMs I often flash the Abyss kernel first and then flash a new ROM from it's recovery. I think the issue is that your ICS ROM was not fully rooted. Try to flash Abyss kernel and the wipe and flash your next ROM.
Click to expand...
Click to collapse
Yes - this way always works for me. flash the abyss kernel in CW and then select reboot to recovery (do not select reboot the phone). When back in recovery, flash a GB ROM
Sent from my GT-N7000 using Tapatalk
Always use redpil from abyss to install a gb when comming from ics.
My Iconia has CWM installed. I used it a while ago to install the leaked ICS rom. I tried to install the most recent (official) ICS rom. Now my Iconia will not boot past the Iconia logo. I've loaded CWM and formatted everything and reinstalled the official rom. No go.
I figure at this point I have to use nvflash to install a new recovery image and rom. Could somebody tell me how to do that and what files to get?
Thanks
Before doing anything else have you tried wiping cache and data? Has worked for me when a rom wont boot. Have you still got cwm can you access it? If no cwm you can accomplish this by holding power and volume up then toggle the rotation lock.
Yes, I have access to CWM. I have tried wiping everything. I even successfully installed a new rom. The device still will not boot past the Acer logo.
I booted wit hte method you described. Two messages appeared in quick succession, "Clearing data..." and "Clearing cache". After the cache message, the device just sits there doing nothing at all.
Previously I had the data partition encrypted. Could that be causing trouble?
did you install an ICS bootloader?
I'm not sure. That is why I created this thread. I'm looking to get the recovery and OS image necessary to get this device working again.
As the previous poster noted, have you switched to the ICS bootloader? When I flashed my A500 with an ICS rom it too got stuck in a bootloop. I then discovered that I actually had to flash the ICS bootloader berfore installing the new rom.
vangorra said:
My Iconia has CWM installed. I used it a while ago to install the leaked ICS rom. I tried to install the most recent (official) ICS rom. Now my Iconia will not boot past the Iconia logo. I've loaded CWM and formatted everything and reinstalled the official rom. No go.
I figure at this point I have to use nvflash to install a new recovery image and rom. Could somebody tell me how to do that and what files to get?
Thanks
Click to expand...
Click to collapse
You can't install official ROM with CWM. You need Acer recovery! This issue has been answered several times. Use search button!!!
Hi,
I ve done dozens of flashing with my Sony and Samsung phones with no problem. Today i decided to flash something fresh on my acer a500 tab. I did my first mistake Please help cause im reading threads for 3 hours now and i dont know how to proceed.
Heres the story:
I was on stock ics 4.0.3 rooted. I used successfully the AfterOTA tool and flashed Bootloader ics v3.14.8 + Recovery Ra v3.1.7 That gave me the Skrilacs Recovery V8.
Then i did all the usual wipes and flashed successfully RE-FLEX XX 40.4 Rom. After the first boot i noticed that my internal storage wasnt empty. It gave me only 14gb free. There were still stuff in like photos, some music and apps remainings. I desided to wipe again and reinstall the rom. I did it a couple of times and i got the same result (internal storage was still with the same stuff).
On my last try to install the rom again it stucked on rom booting screen (bootloop). I can still get into CWM but cant find a solution.
Thanks in advance for any help..
Update: just managed to get it boot back on stock. My heart is back to its place now.
Thanks
Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.
I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija
uglyjohny said:
I quess you renamed stock rom to update.zip and than flashed it? If you havent do it, put it on sd card and pres power+vol down (if nuttin happens than vol up). That shld trigger flashing proces
poslato sa elmag radija
Click to expand...
Click to collapse
I don't have access to a micro sd card reader if the file must be placed on the micro SD card. I already have flashed the stock rom supposedly via TWRP, so I shouldn't have to flash it again, I wouldn't think. If I do, I guess I'll have to get a reader.
Yes. Micro sd. Rename it. You have guodes gere on xda. Im hoping it will help you.
poslato sa elmag radija
It didn't work. Still in same state as before.
I also have access to fastboot if that would help.
m27frogy said:
Simply put, this is what happens when a rooting newbie discovers custom bootloaders and ROMs.
Current State:
A full stock ROM installed (no root) with the Skrillax V8 bootloader plopped on top of it. (which of course means the recovery-from-boot.p file still exists and that I don't have CWM.) The tablet will show the Acer logo then the Android logo and will give the appearance of booting. Then the icon flashes. It does this intermittently and forever.
What I want:
CM 10+ running with Skrillax and TWRP stably. I'd go with Flexreaper for next choice. Maybe I'll try to compile a KitKat version for it someday. Who knows.
How I managed to get my tablet in this crappy state:
Rooted tab a long while ago with a probably far outdated method.
Looked all over the internet later on how to unlock the bootloader and settled on the manual method in this excellent thread.
I flashed V8 and TWRP without a hitch using nvflash.
I wiped and installed Flexreaper.
I liked it but wanted a higher prize. I make a nandroid backup of it onto the external_sd and wiped and installed CM 10.1 from this thread.
This is where everything started going sour. It told me the install was invalid halfway. Disappointed, I wiped again and tried to restore my nandroid backup. It seemed to restore properly, but then Skrillax hung forever loading the kernel.
I wiped again and installed Flexreaper fresh. This time it booted. I downloaded the newest unofficial version of CM they mention on their wiki.
Booted to recovery and installed CM 10. It ran fine and I was impressed with the new OS. Then I noticed the apparent lack of Gapps.
I flashed the Gapps Jellybean package and rebooted. Skrillax hung.
Wiped everything I could fine in the TWRP menu and installed Flexreaper. Got past the primary kernel loading but the android icon would work for a bit then flash, starting all over again.
At this point I flashed several other recoveries, hoping it was my recovery. No such luck. I tried all of them included in V8.
Then finally, I downloaded full stock ICS and flashed it. I rebooted and noticed the same Android flashing thing.
Finally, I flashed V8 again, being the newbie I was, and then suddenly remembered while trying to boot to recovery that the Full install probably rewrote the recovery-from-boot.p.
And here I am.
Tl;dr version:
Went click-happy with ROMs, wiping, and recovery flashing until I was left with a stock OS that wouldn't boot with a Skrillax bootloader but no recovery.
The good news is, I still have cpuid+sbk, it still boots to APX (no idea how I didn't screw that up too.), and I have a nandroid backup on my external_sd which is probably untouched, since I was careful to not wipe it in TWRP.
Please help me fix this. I don't want an excuse to waste money on a flashy new Nexus or Asus Transformer tablet, I already have too many for my wallet's comfort.
Click to expand...
Click to collapse
Babsector should still work - you would need t do a search for it
It seems to have worked properly, sort of. Flashing FLEXReaper results in an "Encryption failed." prompt at boot, which the button, of course, does not work. Wiping everything works except that the prompt notes "E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p4" Trying to reflash V8 with TWRP with the V8.bat file fails at format. More help?
My tablet is still displaying "Encryption failed", the button still doesn't work, and I still love my a500. Help?
Anyone?
I guess I'm screwed, then.
In the end, I think my data partition failed. Formatting or wiping data fails and when installing FlexReaper, it reports /data size as -1. Unless anyone knows how to fix flash memory, I think I'm stuck.
Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Nepoznati said:
Dear XDA
I have been an android user for many years and rooting has been one of the things I always did to my devices. I am an owner of a Note 3, which I have rooted succesfully and used X-NOTE 13 rom for long time. Last week I wanted to try something new and after that everything seems to be impossible. Before I install any roms I always perfom full wipe of, system, data, cache, dalvik cache etc. (I do it inside the recovery). Afterwards I tried to install CRASH ROM V9 and the progress went fine. When the phone rebooted the strange things started to happened I couldn't find the rom's extra menu and couldnt find any of the functions that the rom contained. I just thought that it was problem with the rom itself therefore I tried to went back to X-NOTE, but without any luck. The X-NOTE installed probably but I couldnt boot into it, it was stucked at the "Samsung Note 3" logo. I tried to wipe cache and dalvik but without any luck and every time I rebooted from the recovery the recovery says "it seems your device doesnt have root access" and the recovery tries to gain root access.
Then I couldnt understand anything of what was happening so I went to stock using ODIN. After installing stock rom I used CF-ROOT and everythings went smooth and I could use SuperSU inside the stock rom. Then I installed a recovery and it didn't mentioned anything about root access, so I was ready to install my custom rom...at least I thought so....I installed X-NOTE again (because I knew that this rom worked before without any problems) and after the progress was done I couldnt boot into the rom again, it was stucked. I wiped the cache and dalvik and as soon I clicked reboot in recovery it tells me that I am not rooted.
Then I did the same thing again, went back to stock, installed CF-ROOT and recovery. This time I installed CRASH ROM instead and I could boot into the system, but the rom still misses the "rooted features" etc.
In other words, what have I done wrong? I cant seem to find the problem and I think that I have tried every possible solution?
Informations:
Model: SM-N9005
STOCK ROM: Tried both N9005XXUENB4 (German) and N9005XXUENC2 (Nordic firmware)
Custom Rom: Tried both X-NOTE and CRASH ROM
Recoveries used: TWRP, CWM and Philz CWM
Kernels: Tried with stock one and X-NOTE kernel 1.5
I hope you can help me I cant live with stock roms
Thanks in advance
Regards,
Nepoznati
Click to expand...
Click to collapse
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
antique_sonic said:
weird.
all the rom you mentioned xnote & crash come with root access inside.
When you said you used all those 3 recoveries, did you try each rom with each recovery ?
and when you flash those rom, did you follow to do a clean full wipe as mentioned on each OP thread ?
clean full wipe is not only wipe cache and dalvik, but also the data (factory reset).
Click to expand...
Click to collapse
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Nepoznati said:
Yes I have and tried several other combinations too. First time I installed X-NOTE I wiped everything and installed X-NOTE without problems.
I cant seem to break the code, I am getting frustrated hour by hour. I have double checked everything, I am on the NC2 bootloader with the NC2 kernel, when trying to install X-NOTE I get stuck at "Samsung Glaxy Note 3" - I cant understand what the problem may be and it is beginning to be personal :/ heheh
But seriously what could I have done wrong?
Click to expand...
Click to collapse
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
SOLVED
antique_sonic said:
To be frank... I have no idea. U flash before earlier, means u know how to flash it.
What I could think of, is just the recovery.
I ve been using cwm chenglu all this time (the one reported with less bugs, and most recommended at any rom thread). And jump from rom to rom every 1 week at least with no issue.
I will try tonite use twrp to flash rom. I will let u know if I face any problem.
Click to expand...
Click to collapse
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Nepoznati said:
Finally, finally and finally solved!
Well it seems strange but the problem was the official kernel inside the stock roms that made it almost impossible to run any custom rom.
What I did to solve the problem:
1. Went back to stock rom using a rom with the newest baseband NC2, ex. N9005XXUENC2
1a. I did have som problems getting the bootloader updated, which means I was force to install it over ODIN 3.09 - use this bootloader NC2 BOOTLOADER (Thanks soloilmeglio for the bootloader)
2. I used CF-ROOT to gain root access
3. Then I installed CWM 6.0.4.8 recovery as recommended from antique_sonic (Updated few hours ago!)
4. Install the CivZ-SnapKat-Rev3.1-sm_n9005-4.4.2.zip kernel
5. Lets the phone reboot and check that everything works!
7: Boot into recovery and wipe system, data, cache, dalvik cache
8. Install the custom rom
Dont ask me why the kernel wasn't working from beginning and why it was "corrupted" after installing another custom rom - but now everything works as it should!
Thank you very much antique_sonic for helping me!
Click to expand...
Click to collapse
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
antique_sonic said:
Good then to know ur phone is okay.
I fully wipe with twrp last nite. And flash xnote. Hang at boot after done.
Fully wipe again, and flash assassins. A lot fc here and there.
I flash back cwm chenglu, full wipe, and flash back xnote. Now it runs nicely.
My phone not suit with twrp.
Click to expand...
Click to collapse
It could probably be a problem with TWRP as you mentioned earlier. After using CWM everything went smooth after updating my kernel. Last night I couldnt hold me back to try one more time, and I flashed X-NOTE with TWRP and I got the same problem as described in #1 post. Then I installed CWM and flashed X-NOTE again and everything got messed up. Then I restored everything, force installed the kernel and bootlaoder. After that installed CWM and then I was able to run X-NOTE without any problem.
I am not a professional developer but I may think that the problem is TWRP when it tries to flash the kernel under the process with may results in some problems. When using CWM from the beginning I do not get any problems but when using TWRP I need to restore everything back.