Develop Bugs

[Q] Status 7 Error?

I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:

Improper recovery.

samelaryan said:
I know this has been asked hundreds of times, and i searched the forums for days for a way to fix it, but with no use.
I have a rooted AT&T Galaxy SIII with JB 4.1.1. I am trying to install the CM 10.1(4.2.2) Nightly version, but i always get the infamous "Status 7 Installation Aborted" error.
Yes i am sure im downloading the correct ROM zip file for my phone and carrier.
I have CWM 6.0.2.1, and i followed the steps correctly. (Clear data -> Clear Cache Partition -> Clear Dalvik Cache -> install ROM)
I have tried so many times, i also re-rooted my phone, reinstalled CWM, and redownloaded different nightly versions of the ROM, as well as other ROMS like JellyBam.
I also tried to delete the assert lines in the update-script file, but that also wouldnt work.
Thank you. :good:
And please dont hate on me, im new to rooting and flashing. :crying:
Click to expand...
Click to collapse
BAM1789 said:
Improper recovery.
Click to expand...
Click to collapse
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers

xBeerdroiDx said:
if you can boot into the phone, download ROM manager and update your cwm recovery. latest version is 6.0.2.8.
CM10 and 10.1 are picky about you having the most recent version. cheers
Click to expand...
Click to collapse
I did that and it worked thank you :good:

samelaryan said:
I did that and it worked thank you :good:
Click to expand...
Click to collapse
thats what we're all here for, buddy

Status 7: installation aborted.
xBeerdroiDx said:
thats what we're all here for, buddy
Click to expand...
Click to collapse
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.

perceptorz said:
Hi guys, I'm having same issue but on N7000 international version. I'm able to go in the recovery mode and download mode but phone won't boot normally. It's stuck on Samsung logo so can you please advise something? How can I update CWM if that's the issue. I was on ICS 4.0.4 XXLRK before trying to install CM10.1 on Note.
Thanks in advance for your help.
Click to expand...
Click to collapse
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot

xBeerdroiDx said:
I would be doing my research in an N7000 forum, friend.
Also, your post seems confusing as you seem to be saying you also got a status 7 error but then you appear to have installed abroad and are stuck at the boot logo. If you successfully flashed the correct rom for your device without any errors, pull battery, replace and wipe data in recovery. Reboot
Click to expand...
Click to collapse
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.

perceptorz said:
Apologies for both confusion and using the S3 that to find some help. I just found the situation quite familiar so I couldn't help myself from asking the question
On the situation, I was able to install CWM and am able to go to recovery or download mode but the error displays when I try to update the zip of any rom.
Click to expand...
Click to collapse
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.

xBeerdroiDx said:
If the phone itself is functioning fine but you simply cannot flash a new rom or rom update, you need to update your recovery. Go to clockworkmods website and download version 6.0.1.2.
Click to expand...
Click to collapse
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)

perceptorz said:
Right now, phone doesn't get pass Samsung boot logo so will I be able to update new CWM using Odin? (Sorry, if the question appears to be basic or stupid)
Click to expand...
Click to collapse
I would take up this situation in the correct forum. The more we discuss your device issues the more likey you are to download the wrong file or use a procedure not designed for your device software.
If you came from stock, flashed a rom and are stuck at the samsung logo, boot into recovery, wipe data and cache. Reboot to see if that helped. If not, seek advice in the N7000 forum. Cheers

Thanks for the guidance.

help android 4.3 stuck at google screen

Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...

antwong45157 said:
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
Click to expand...
Click to collapse
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?

Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?

antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload

Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
Woodyy said:
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Click to expand...
Click to collapse
Going to try to side load first with twrp. If all else fails gonna try cwm recovery

Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*

antwong45157 said:
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
Click to expand...
Click to collapse
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.

Woodyy said:
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Click to expand...
Click to collapse
I tried flashing paranoid android 3.94 which is android 4.3 with adb. Hoping it would work different . Nope same result.
I am able to get back on 4.2.2 using adb. I'm on 4.2.2 typing this message . I just need to find out why I can't get on 4.3 with getting stuck at boot screen

This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app

Jewveeski said:
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe my boot loader is unlocked. When. I reboot I see he unlocked lock. But I did flash the new boot loader so maybe I would have to re unlock it? I will try the ROM you posted

Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!

itslels said:
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
Click to expand...
Click to collapse
I had the issue when I tried to go directly from 4.2.2 to a 4.3 custom. The only thing that cleared it up was flashing stock 4.3 from google. After that, no more problems.

Hmm wonder what could be causing it. I did have this issue going from 4.2.2 to 4.3. Every 4.3 ROM I have flashed has booted.
toro, toro!

I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )

antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
i have the same fuking problem , what did you do ?

antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Gz dude enjoy 4.3

antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Thanks, I followed this and finally managed to get to 4.3
http://forum.xda-developers.com/showthread.php?t=2389721

Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
EDIT: I did a reboot when I got home and it booted up fine, although I felt like it took longer than on previous versions.

oynoy said:
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
Click to expand...
Click to collapse
Gotta be able to reboot your phone brother lol. Give it a shot. If it locks up there is always a way to fix the issue... Good luck. Best wishes

FIX for issue getting stuck on google screen after 4.3 reboot
I don't know if anyone has posted this elsewhere. I had the same problem yesterday - after a lot of playing around this is how I fixed it:
***Note1: you need adb and fastboot.
***Note2: make external backup of things (i.e. photos) you want to keep using adb.
Procedure:
1. Download 4.2.2 image from google (can't post link because of spam prevention rules - you can search for "google developers nexus images")
2. extract files to location of choice
3. Download latest custom recovery image of your choice. I prefer TWRP (latest 2.6)
3. reboot to recovery, do a full factory reset (wipe everything, you will lose all your storage).
4. Reboot to bootloader (from phone off, power plus volume rocker).
5. flash stock image via fastboot (change names and paths acordingly):
Code:
fastboot devices (make sure fastboot can see your device)
adb reboot bootloader
fastboot flash bootloader bootloader-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio /path/to/radio-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio-cdma /path/to/radio-cdma-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot -w update /path/to/image-mysid-<version>.zip
5. After this last step, the phone should reboot.
6. Go through the phone setup process.
7. power off, and boot to bootloader
8. flash custom recovery:
Code:
fastboot flash recovery /path/to/custom-recovery.img
9 reboot to recovery. TWRP will ask you if you want to root when you reboot to system.
10. Phone rooted and like new!
I think that is all - you can flash your ROM of choice after this!

Need some help with my new Nexus 7

I just got a new Nexus 7 today and naturally, my first goal is to unlock and root.
I started by booting into the bootloader and doing "Fastboot oem unlock"
I said yes, wipe and it said it worked fine.
After that I installed the latest TWRP for the Nexus 7 2013
It installed just fine and i installed supersu 1.69 through it
for some reason it is stuck at the boot animation now and in TWRP it says 0 internal storage space and fails whenever i factory reset.
what can I do to fix this?

fenguepay said:
After that I installed the latest TWRP for the Nexus 7 2013
It installed just fine and i installed supersu 1.69 through it
for some reason it is stuck at the boot animation now and in TWRP it says 0 internal storage space and fails whenever i factory reset.
what can I do to fix this?
Click to expand...
Click to collapse
Did you try installing TWRP again?

meekrawb said:
Did you try installing TWRP again?
Click to expand...
Click to collapse
yes and i also tried installing cwm recovery too. no luck with either. im currently trying to reboot after re-unlocking.

fenguepay said:
yes and i also tried installing cwm recovery too. no luck with either. im currently trying to reboot after re-unlocking.
Click to expand...
Click to collapse
Wiping data doesn't work?
You MAY have to flash back to stock and start over.
Other people have had this problem, check here:
http://forum.xda-developers.com/showthread.php?t=2380913
Keep in mind that that thread is from before Google released the factory images. Hopefully it can help you out though.

You can also try one of scrosler's pre-rooted stock ROMs. I'd recommend using fastboot to wipe cache, system and userdata to be on the safe side.
http://www.scottsroms.com/downloads.php?do=cat&id=94

http://forum.xda-developers.com/showthread.php?t=2381582 fixed it

[Q] struck at logo screen while installing rom HELP PLEASE

I HAD A HTC ONE V. ROOTED IT SUCCESSFULLY AND THE TRIED TO INSTALL CUSTOM ROM WITH Primou Omega 2.4.0 - Stable Release 1
BUT STRUCK AT LOGO SCREEN, PLEASE HELP ME. M USING TWRP RECOVERY

jim370 said:
I HAD A HTC ONE V. ROOTED IT SUCCESSFULLY AND THE TRIED TO INSTALL CUSTOM ROM WITH Primou Omega 2.4.0 - Stable Release 1
BUT STRUCK AT LOGO SCREEN, PLEASE HELP ME. M USING TWRP RECOVERY
Click to expand...
Click to collapse
1) Flash proper kernel (Hellboy is for Ptimou Omega as I remember), you have to find it on this forum by yourself
2) Go to recovery, make a full wipe and flash ROM again

jim370 said:
I HAD A HTC ONE V. ROOTED IT SUCCESSFULLY AND THE TRIED TO INSTALL CUSTOM ROM WITH Primou Omega 2.4.0 - Stable Release 1
BUT STRUCK AT LOGO SCREEN, PLEASE HELP ME. M USING TWRP RECOVERY
Click to expand...
Click to collapse
It's so easy, you just have to read a bit...
Like: http://forum.xda-developers.com/showthread.php?t=1996665
or all other tutorials available, if you read threads... :fingers-crossed:
Just don't give-up! Hov is still alive!!! :victory:

bratusm said:
It's so easy, you just have to read a bit...
Like: http://forum.xda-developers.com/showthread.php?t=1996665
or all other tutorials available, if you read threads... :fingers-crossed:
Just don't give-up! Hov is still alive!!! :victory:
Click to expand...
Click to collapse
Yeah, for sure...

parkourz said:
Yeah, for sure...
Click to expand...
Click to collapse
Wonderfull...

parkourz said:
1) Flash proper kernel (Hellboy is for Ptimou Omega as I remember), you have to find it on this forum by yourself
2) Go to recovery, make a full wipe and flash ROM again
Click to expand...
Click to collapse
thanks it worked

now im trying to restore to my original rom using twrp recovery can u please tell me which kernel to use

jim370 said:
now im trying to restore to my original rom using twrp recovery can u please tell me which kernel to use
Click to expand...
Click to collapse
Stock (original). If you had backed up your original ROM selecting backuping boot partition, system partition, data partition and cache partition, you don't have to flash stock kernel. While flashing kernel, it's "installing" on boot partition... I hope you can understand me

parkourz said:
Stock (original). If you had backed up your original ROM selecting backuping boot partition, system partition, data partition and cache partition, you don't have to flash stock kernel. While flashing kernel, it's "installing" on boot partition... I hope you can understand me
Click to expand...
Click to collapse
In English- If you did a normal full backup no need for new kernel it will get reflashed by TWP recovery.

mcgi5sr2 said:
In English- If you did a normal full backup no need for new kernel it will get reflashed by TWP recovery.
Click to expand...
Click to collapse
Exactly

ok, so I have the same problem. I downloaded this rom twice, flash it and my HOV stay on lock screen. I used Kernel from "Features" at Primou Omega 2.4.0 post. Is it correct ? Or maybe I must use another kernel ?

parkourz said:
Stock (original). If you had backed up your original ROM selecting backuping boot partition, system partition, data partition and cache partition, you don't have to flash stock kernel. While flashing kernel, it's "installing" on boot partition... I hope you can understand me
Click to expand...
Click to collapse
i did the recovery and the phone recovered but when i tried to restart the phone it struck at htc logo screen again any idea what happened

jim370 said:
i did the recovery and the phone recovered but when i tried to restart the phone it struck at htc logo screen again any idea what happened
Click to expand...
Click to collapse
In post #3 I wrote that you have to read a bit and I gave you link. You didn't even read read OP there, otherwise you should find something interesting after those words: Stuck in Bootloops, Cant Pass the HTC welcome Screen (in light blue bold font...)
Or, if you'd follow my idea to read other tutorials, you could find that one: http://forum.xda-developers.com/showthread.php?t=1706070 and that one will definitely help. :fingers-crossed:

BOOT LOOP
parkourz said:
1) Flash proper kernel (Hellboy is for Ptimou Omega as I remember), you have to find it on this forum by yourself
2) Go to recovery, make a full wipe and flash ROM again
Click to expand...
Click to collapse
phone doesnot go to recovery mode or fastboot mode. please help

thanks everyone
now my phone is working perfectly

Failed install of Android 7.1.2 - boot stuck on "Android"

I had CWM Recovery and an older cyanogenmod rom installed and I wanted to upgrade to 7.1.2 from here: https://forum.xda-developers.com/lg.../rom-android-7-0-nougat-20161008-r16-t3476750
I copied the rom to internal memory, rebooted into recovery, selected the rom file to install. It showed some messages about patching, then in a couple of minuted erred with smth like "Erro loki-ifying because of incompatible aboot image".
I then rebooted and now it boots and shows "ANDROID" and is stuck on it - looks like it partially updated the ROM and failed somewhere.
I am not sure what to do now - I tried to boot into recovery (Power off -> Hold Power + Vol down till menu shows) but it doesnt work - it keeps booting onto this stuck boot.
Any ideas?

As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Sent from my XT1254 using Tapatalk
Crap. Sorry. Disregard. Thought this was a Droid Turbo thread.

Einsteindks said:
As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Click to expand...
Click to collapse
But how do I flash anything if I can't get into recovery?

andreyl79 said:
But how do I flash anything if I can't get into recovery?
Click to expand...
Click to collapse
You missed my edit update. I got confused as to which thread I was replying to.
Sent from my XT1254 using Tapatalk

Einsteindks said:
You missed my edit update. I got confused as to which thread I was replying to.
Click to expand...
Click to collapse
Nevertheless you gave me the idea to try looking for a similar LG recovery tool and I just found one. Flashing stock at the moment - fingers crossed

Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here

andreyl79 said:
Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here
Click to expand...
Click to collapse
The reason the flash failed is simply the fact you put the ROM on the internal storage, flashing from there wiped the ROM before it gets written. If you had stored the AOSP on an external SD, it would have worked.
As Lineage is based on AOSP, it should have failed also...