Database Develop

[Q] how to identify my problem with flashing roms?

i have been flashing roms now since january this year. I've already flashed a lot for both the Gio and the Ace.
Now I'm running into this same problem again with several roms:
when I want to flash the rom, it returns me a status 7 error. Why? I don't know. I've tried already so much: md5 checksum, downloading again, formatting my sdcard partition
I have it with many roms (cm 7 blackhawk / firekernel, cm 10.1.1 mardon, cm10 maclaw etc etc).
I would like to find out what the problem is and possibly how I can solve it.

Maybe there is a problem with your recovery install. You could try to install that again.

Try to toggle signature verification in cwm. Or just reflash the recovery.
Sent from my Galaxy Ace GT-S5830 using xda premium

Venomous Viper 119 said:
Try to toggle signature verification in cwm. Or just reflash the recovery.
Sent from my Galaxy Ace GT-S5830 using xda premium
Click to expand...
Click to collapse
should i download a new recovery or the same i already had? (file name: recovery-clockwork-5.0.2.6-galaxyace-fix.zip)

DutchArjo said:
should i download a new recovery or the same i already had? (file name: recovery-clockwork-5.0.2.6-galaxyace-fix.zip)
Click to expand...
Click to collapse
Just download the same file again. I use the same one.

nikwen said:
Just download the same file again. I use the same one.
Click to expand...
Click to collapse
thanks. I've tried this but even reflashing my cwm file returns a status 7 error
but flashing my px-cwm v2.zip recovery completed.
I managed to install cwm 6.0.3.2 (although it still says 5.0.2.6) and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?

DutchArjo said:
thanks. I've tried this but even reflashing my cwm file returns a status 7 error
Click to expand...
Click to collapse
Ok. In that case there is an error with your recovery.
@The Others: Would it help to flash a Samsung Firmware via Odin? Would that replace the recovery?

I managed to install cwm 6.0.3.2 and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?

DutchArjo said:
I managed to install cwm 6.0.3.2 and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?
Click to expand...
Click to collapse
Try it if you know what you are doing.

nikwen said:
Ok. In that case there is an error with your recovery.
@The Others: Would it help to flash a Samsung Firmware via Odin? Would that replace the recovery?
Click to expand...
Click to collapse
Hi nikwen, yes, to flash via Odin will replace the recovery with the stock recovery. Cheers.
Sent from my GT-S5830 with TouchWiz UX 5.0 by NaTHaN

BajoPrimate said:
Hi nikwen, yes, to flash via Odin will replace the recovery with the stock recovery. Cheers.
Sent from my GT-S5830 with TouchWiz UX 5.0 by NaTHaN
Click to expand...
Click to collapse
i've flashed a stock rom with mobile odin.
After that: i've tried to flash the cm10.1.3 rom from mardon. It returned a status 0 error. After that, I've flashed cwm 6.0.3.2 and tried to flash the rom again. Still a status 7 error.
Is it possible that maclaw's cm9 or cm10 have changed something in my Phone which causes that i'm unable to flash anything anymore? I only get status 7 errors. When i follow the suggested steps at XDA to get rid of these errors (read: delete the assert lines in updater script) the status 7 errors are replaced by status 6 errors.
when i'm in cm9 and execute getprop in terminal, the ro.product.build / devide / model = cooper (no gt-s5830).
the label on my Phone (which is located underneath the battery) says gt-s5830.
How do I get rid of the maclaw history and return to the completely Original rom to see if I can flash from there?

DutchArjo said:
i've flashed a stock rom with mobile odin.
After that: i've tried to flash the cm10.1.3 rom from mardon. It returned a status 0 error. After that, I've flashed cwm 6.0.3.2 and tried to flash the rom again. Still a status 7 error.
Is it possible that maclaw's cm9 or cm10 have changed something in my Phone which causes that i'm unable to flash anything anymore? I only get status 7 errors. When i follow the suggested steps at XDA to get rid of these errors (read: delete the assert lines in updater script) the status 7 errors are replaced by status 6 errors.
when i'm in cm9 and execute getprop in terminal, the ro.product.build / devide / model = cooper (no gt-s5830).
the label on my Phone (which is located underneath the battery) says gt-s5830.
How do I get rid of the maclaw history and return to the completely Original rom to see if I can flash from there?
Click to expand...
Click to collapse
Are there differences between Odin and Mobile Odin? If there are some, flashing using the desktop one might help.
Cooper is the codename for our Ace. So that is ok.

I've tried 2 stock roms now. Neither can boot. I've reflashed the 5.0.2.6 cwm recovery because that one is the only one that can restore my cm9 backup. I'm lost... I don't know what to do now because there is simply no way of getting a different rom on this Phone and i would really like to know why.
What did maclaws rom do that f*ck*d up my Phone?

DutchArjo said:
I've tried 2 stock roms now. Neither can boot. I've reflashed the 5.0.2.6 cwm recovery because that one is the only one that can restore my cm9 backup. I'm lost... I don't know what to do now because there is simply no way of getting a different rom on this Phone and i would really like to know why.
What did maclaws rom do that f*ck*d up my Phone?
Click to expand...
Click to collapse
You could send them an email.

Flash stock via PC using odin. You will be stuck in a bootloop. Reboot into recovery & factory reset. Reboot & phone boots. Now, important , you cannot flash custom Roms via stock recovery. Place the cwm 5.0.2.6 zip on sd card. Reboot into recovery , select " install update from sd card ", select the zip file, select yes & reboot. Again reboot into recovery, do full wipes & select " install zip from sd card " & NOT " install update from sd card " & flash any stock based Rom like Touchwiz 5 by Nathan. If you follow this, everything must be fine.
Sent from my Galaxy Ace GT-S5830 using xda premium

nikwen said:
You could send them an email.
Click to expand...
Click to collapse
YEs... I managed to flash px recovery 0.4 (again: I still had to delete the assert lines from updater script). Now I was able to flash the cm 10.1.3 rom from Mardon. Just booted for the first time. Hopefully my status 7 errors are now history... (i don't know if I can restore my cm9 backup from maclaw but we will see).

DutchArjo said:
YEs... I managed to flash px recovery 0.4 (again: I still had to delete the assert lines from updater script). Now I was able to flash the cm 10.1.3 rom from Mardon. Just booted for the first time. Hopefully my status 7 errors are now history... (i don't know if I can restore my cm9 backup from maclaw but we will see).
Click to expand...
Click to collapse
Great.
Do you want to restore it? I prefer 4.2.2.

i prefer not. But it depends on how satisfied I am on this cm 10.1.3 rom. And how many bugs / errors I experience, How smooth/fast it is etc.
When I'm not satisfied, I can Always return to this rom I was most satistied off so far. But I wanted another rom because I have a lot spontaneous reboots when turning on Wifi again....

DutchArjo said:
i prefer not. But it depends on how satisfied I am on this cm 10.1.3 rom. And how many bugs / errors I experience, How smooth/fast it is etc.
When I'm not satisfied, I can Always return to this rom I was most satistied off so far. But I wanted another rom because I have a lot spontaneous reboots when turning on Wifi again....
Click to expand...
Click to collapse
In case like yours a fresh often install helps, too.

nikwen said:
In case like yours a fresh often install helps, too.
Click to expand...
Click to collapse
it might, but it also means reinstalling all my apps again. And I do not want to do that
hopefully, this cm10 rom is satisfying enough. I will then stick to it...

[Q] Bootloop? & failed Cyanogen Installation

Hi, I'm using a N7000, and I think I have a bootloop, but I'm not sure. I tried to install CM9, and followed the guide there:
1. flash hardcore's ClockworkMod Recovery
2. Push CM 9 onto phone using adb
3. Boot in recovery mode
4. Wipe data/factory reset
5. install zip from sd card
6. choose zip from sd crad
7. Select CM9
Then, I see the following on the console?:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
At that point, I found that I could not boot, and if I tried, there would be a yellow triangle with a "!" in it.
What could I do to fix this problem? Thanks!
Edit: Solved by connecting microSD to computer, then transfering the ROM onto microSD, then flashing again.

oswinso said:
Hi, I'm using a N7000, and I think I have a bootloop, but I'm not sure. I tried to install CM9, and followed the guide there:
1. flash hardcore's ClockworkMod Recovery
2. Push CM 9 onto phone using adb
3. Boot in recovery mode
4. Wipe data/factory reset
5. install zip from sd card
6. choose zip from sd crad
7. Select CM9
Then, I see the following on the console?:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
At that point, I found that I could not boot, and if I tried, there would be a yellow triangle with a "!" in it.
What could I do to fix this problem? Thanks!
Click to expand...
Click to collapse
Do you have a nandroid backup?
Something went wrong when pushing via adb.
You probably should have just copied it over before wiping your current ROM.
Anyhow we can easily fix this...just answer my question above first and we will go from there.
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta on a dual boot system running fully featured Ubuntu touch and Firefox OS

AndroidSlave said:
Do you have a nandroid backup?
Something went wrong when pushing via adb.
You probably should have just copied it over before wiping your current ROM.
Anyhow we can easily fix this...just answer my question above first and we will go from there.
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta on a dual boot system running fully featured Ubuntu touch and Firefox OS
Click to expand...
Click to collapse
Well, I'm not sure if I have a nandroid backup, but I did backup using cwm before I wiped.

oswinso said:
Well, I'm not sure if I have a nandroid backup, but I did backup using cwm before I wiped.
Click to expand...
Click to collapse
Then you should restore it and download the cm ROM di4ectly to the device and flash it after full wipes and then flash gapps
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta on a dual boot system running fully featured Ubuntu touch and Firefox OS

AndroidSlave said:
Then you should restore it and download the cm ROM di4ectly to the device and flash it after full wipes and then flash gapps
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta on a dual boot system running fully featured Ubuntu touch and Firefox OS
Click to expand...
Click to collapse
What do you mean by download the cm ROM directly to the device?

Download from your phone...not to you PC, then transfer to phone.
Sent from my GT-P3110 using XDA Premium HD app

oswinso said:
What do you mean by download the cm ROM directly to the device?
Click to expand...
Click to collapse
As in using the web browser on your phone after you restore the backup.
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta on a dual boot system running fully featured Ubuntu touch and Firefox OS

Thanks for the replies, but then I can't get pass the Samsung screen. If I try and turn my phone on, the phone somehow turns itself off, if you know what I mean.
Also, I keep getting the no battery symbol even though my phone is fully charged, and am not quite sure what may be causing this.
Thanks again!

flash philz, hardcores doesnt recognize cm roms well to flash.
Sent from my GT-N7000 using Tapatalk 2

Stuck at Motorola "Dual Core" logo

So my phone is stuck on the Motorola Dual Core logo after trying to flash a 4.4 Rom. I am still able to get to get into my recovery and into fastboot. No matter what rom I try to flash it still seems to go into the boot cycle. I have tried flashing to stock firmware with no luck. Anyone know what I should do?

After trying to flash stock again it seems like it is on but the screen is pitch black. When holding down the power button it gives the the vibrations after a little bit. Really not sure what this means. When plugging the device into the computer when the screen is black windows does recognize that there is a device and plays the noise but it does not show up in the devices list.

penser
ph3dia said:
After trying to flash stock again it seems like it is on but the screen is pitch black. When holding down the power button it gives the the vibrations after a little bit. Really not sure what this means. When plugging the device into the computer when the screen is black windows does recognize that there is a device and plays the noise but it does not show up in the devices list.
Click to expand...
Click to collapse
Is your bootloader unlocked?
What recovery are you using?
What ROM did you try to flash?
How did you flash it?
How are you trying to flash back to stock?

penser said:
Is your bootloader unlocked?
What recovery are you using?
What ROM did you try to flash?
How did you flash it?
How are you trying to flash back to stock?
Click to expand...
Click to collapse
1. Yes
2. Philz
3. OSE Latest nightly 4.4.2
4. Wiped everything and then flashed
5. Using Myth Tools

penser
ph3dia said:
1. Yes
2. Philz
3. OSE Latest nightly 4.4.2
4. Wiped everything and then flashed
5. Using Myth Tools
Click to expand...
Click to collapse
Alright, try flashing back to stock manually. Unzip the .zip, open the .xml in notepad(++) and on every line you'll see something along the lines of operation, partition, img. Open a command prompt in the location of the folder that contains the .xml (not the .zip, shift-click on white space in the folder and click open command prompt window here) and flash each line by typing
Code:
fastboot operation partition img
so each should look something like
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
Just don't do the one that says "GPT_MAIN1.img" or something of the sort (should be one of the first ones). Also type
Code:
fastboot -w
before you start.

same problem...
Hi all,
I have the same problem... I cannot flash CM 11.0 builds. In the first boot it works, but if you reboot, it will get stuck in Motorola's logo.
I also tried to restore original images (using sbf dot droid-developers dot org / phone.php?device=7 AT&T 4.1.1 image), but with no success.
CM 10.1 build works fine, so that's odd.
My fastboot bootloader says:
"
AP Fastbot Flash Mode (NS)
10.9B(*) (sha-2e68372 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is UNLOCKED, Status Code: 1
...
"
Is your bootloader unlocked?
Yes
What recovery are you using?
Tried CWM 6.0.38 and Philz latest.
What ROM did you try to flash?
CM 11.1 nightly (cm-11-20131217-NIGHTLY-mb886.zip)
How did you flash it?
Wiped everything and then flashed
How are you trying to flash back to stock?
Using RSD Lite.
Thanks very much!

Did you try updating to Phiz latest here: http://forum.xda-developers.com/showthread.php?t=2552622
It is my understanding that the latest CWM is required to flash 4.4 and higher roms.

audit13 said:
Did you try updating to Phiz latest here: http://forum.xda-developers.com/showthread.php?t=2552622
It is my understanding that the latest CWM is required to flash 4.4 and higher roms.
Click to expand...
Click to collapse
Yes, I downloaded it last night... Is it better to use Philz or pure CWM?

My atrix HD broke however when it was working I was able to get cm11 on it by flashing using this recovery:
http://forum.xda-developers.com/showthread.php?t=2421418
When flashing cyanogen mod, wipe EVERYTHING basically /system /cache dalvik and then storage as well, this prevents the emulated/0/0/0/0/0 directory type of thing from happening, then after flashing factory reset clear cache and wipe dalvik then start up the phone. This has always worked for me and makes a squeaky clean install
Sent from my Nexus 10 using XDA Premium 4 mobile app

jubarim said:
Yes, I downloaded it last night... Is it better to use Philz or pure CWM?
Click to expand...
Click to collapse
I currently use Touch CWM which Philz is based upon. From my experience, the latest release for both will do the job.

anthony2424 said:
My atrix HD broke however when it was working I was able to get cm11 on it by flashing using this recovery:
http://forum.xda-developers.com/showthread.php?t=2421418
When flashing cyanogen mod, wipe EVERYTHING basically /system /cache dalvik and then storage as well, this prevents the emulated/0/0/0/0/0 directory type of thing from happening, then after flashing factory reset clear cache and wipe dalvik then start up the phone. This has always worked for me and makes a squeaky clean install
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man!! That really worked!

jubarim said:
Thanks man!! That really worked!
Click to expand...
Click to collapse
You're welcome, glad to help
Sent from my Nexus 10 using XDA Premium 4 mobile app

Root, Backup & ROM Verizon LG G2 on 4.4.2???

I can't seem to find a process for backing up my current "stock" setup, then rooting it and installing TWRP and ROM's.
I had a G2 previous to it getting kitkat and had done all of this with that, fairly easily too...but can't seem to find the same process to do it after the kitkat update (4.4.2)...?
Any help would be greatly appreciated.

sdgmcdon said:
I can't seem to find a process for backing up my current "stock" setup, then rooting it and installing TWRP and ROM's.
I had a G2 previous to it getting kitkat and had done all of this with that, fairly easily too...but can't seem to find the same process to do it after the kitkat update (4.4.2)...?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You need to root it (using ioroot), install a recovery (using autorec) then you can back it up.

mjones73 said:
You need to root it (using ioroot), install a recovery (using autorec) then you can back it up.
Click to expand...
Click to collapse
This worked to get twrp on it thanks! ks (i was able to eventually get it rooted using ioroot and did a nandroid backup), i am however not able to flash a new rom (using cm's latest nightly for the vs980 now...going to try the snapshot next, but the nightly just fails almost immediately and i did have twrp fix permissions????
thanks again!
EDIT: And crap, stuck in a boot loop...said it flashed the snapshot ok, almost immediately, rebooted and boot loop.

mjones73 said:
You need to root it (using ioroot), install a recovery (using autorec) then you can back it up.
Click to expand...
Click to collapse
It's official, I'm bricked...lg logo boot loop, nothing else. Somehow in the process my nandroid and twrp backups no longer show up in twrp either (have to do the factory reset (hold down vol down and power twice, then power twice to confirm reset)...I've looked in the backup folders using twrp file manager and the folders have lots of stuff in them (not sure if it's correct stuff though?) and the folders are named as I named them when I did the backups...also, most other data seems to be on the phone and only 13gb's free according to twrp, so has to be a "system" there, but just get boot loop...
I've since read that the cm builds dont work on 24a kk 4.4.2 vs980; results in boot loops, but I can't get adb to work either so I can't even download a different rom to get it going...
I'm stuck...way stuck....

sdgmcdon said:
This worked to get twrp on it thanks! ks (i was able to eventually get it rooted using ioroot and did a nandroid backup), i am however not able to flash a new rom (using cm's latest nightly for the vs980 now...going to try the snapshot next, but the nightly just fails almost immediately and i did have twrp fix permissions????
thanks again!
EDIT: And crap, stuck in a boot loop...said it flashed the snapshot ok, almost immediately, rebooted and boot loop.
Click to expand...
Click to collapse
Did you use jackpotcalvin's cm11? If not then you're in a bootloop because the official cm11 for our phone users 4.2.2 kernel base, whereas jpc's uses kk kernel.
Can you get into download mode? If so, return to stock using kdz or tot method (I've used tot, fairly easy).
Sent from my VS980 4G using XDA Premium 4 mobile app

ADB Sideload may work for you.
http://teamw.in/ADBSideload
Boot into TWRP, Advanced, ADB Sideload.

[Q] Help! Trouble Flashing on sm910T

Was previously rooted running a flashed rom (firekat deodexed v7), but had to restore, when trying to update to newer version of this rom, wouldn't update. So i restored to stock 4.4 kitkat ank4 and then did the upgrade thru tmobile to lollipop. I then rooted again with cf root and flashed recovery with flashify, everything went smooth. Tried flashing new rom and it will not flash any rom. (tried beanstalk 5.0050-20150414-trltetmo, cmremix_trltetmo-5.0.2.v6.0.zi0,959, cm-12.1-2015050 and cm-12-20141220-unofficial-trltetmo, darthstalker_note4-v1 and some others. Did full wipe, cache, dalvik, etc, .
Have then restored to stock n910t-cod6 lollipop. Cf root and flashify twrp. Did backup and also restore from backup will also not work, just goes into bootloop.
Also did a full restore/wipe from settings on phone.
When flashing, keep getting error "unable to open zip file" - error flashing zip 'external_sd/beanstalk-5.0050-20150414-trltetmo.zip"
updating partition details

Try a different copy of the team win recovery.

Maybe a different version, not a different copy, but yeah that.

Are you waiting long enough at boot? It literally takes 15-20 mins to boot.
Did you try putting your zip directly on the sdcard (device memory).?

Recovery
10-K said:
Try a different copy of the team win recovery.
Click to expand...
Click to collapse
I've tried CWM also, think I should try different versions of both or any other ideas?

Verify the MD5 of the ROM you downloaded.
Sent from my SM-N910T using XDA Free mobile app

Try moving file to int sd card and install from new location.

Matching MD5
nosympathy said:
Verify the MD5 of the ROM you downloaded.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
Checked and they match