I was trying to install Redemption 2.4 according to these instructions.
dimedroid.blogspot.com/2010/12/dimes-rooting-guide-for-droid.html?showComment=1299665643877#c7756561560124612339
Well I got it to semi installed I think. When it was installing after step 4: Kernal, it said an error and that installation was aborted. When I rebooted it stayed on the Android screen for half an hour. I then restored it to a back then went through the Rom Manager and tried to install it that way but I still received there error but this time it did start in Redemption and it did say it was a success on the loading up screen. Is there anyway to figure out if anything is missing? Or should I just keep installing it until it actually completes the process correctly?
You may have a corrupt download, I would download it again and reinstall. Did you look at the thread on xda?
Don't use that guide and use one here on XDA, that has an insane amount of "steps" to take for no reason.
I did download the one from here.
I will look for the guide here, the one in the Redemption 2.4 thread looks pretty simple, not sure if there is more to that. I keep getting this error on installation after Step 4.
assert failed: write_raw_image("/tmp/boot.img".
"boot")
E:Error in /sdcard/Redemption_Rom_2.4_FINAL.ZIP
(Status 7)
Installation aborted.
Ciresamor said:
I did download the one from here.
I will look for the guide here, the one in the Redemption 2.4 thread looks pretty simple, not sure if there is more to that. I keep getting this error on installation after Step 4.
assert failed: write_raw_image("/tmp/boot.img".
"boot")
E:Error in /sdcard/Redemption_Rom_2.4_FINAL.ZIP
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I too am getting this error. Although it's not all inclusive to Redemption Rom. I've tried others as well and get the same error when it tries to flash the kernel. I've tried it with CWM 3.0.0.5, 3.0.0.8, 2.5.0.5...almost all of them. Currently have a backup with IncRom 1.4 that i keep going back to but just curious if there's a common ground here maybe with a certain kernel installed already/CWM version....anything.
So I've been trying to fix this problem for about 6 hours now and still no luck.
I am very new to this stuff which is probably why I made the mistake. Basically I was trying to install CyanogenMod 10 custom ROM on my phone and I kept receiving this "status 7 error" I did some research on how to fix that, and that's when the problem occurred.
I read that I should clear my Dalvik cache, /system, and do a factory settings wipe. I did all that, continued to get the error, and when I rebooted I was stuck on the boot screen, my theory is that it had something to do with the clearing of the /system, but I don't know.
I can still get into download mode and into the CW recovery, but that's about it. I tried flashing the stock firmware through Odin, but the firmware I downloaded is just a .zip, and there is not .tar when you extract it, so I cant use Odin. I am at a total loss here, please help me.
Thanks a lot in advance.
Have you tried re-downloading the ROM, and flashing the new zip? Your current zip may be corrupt.
LordDiabeetus said:
Have you tried re-downloading the ROM, and flashing the new zip? Your current zip may be corrupt.
Click to expand...
Click to collapse
Where would I download the zip to? I can only access the files that are on my phone through CW. I cannot or at least I do not know how to transfer files to my phone in its current state.
Thanks for the reply.
apolanco115 said:
Where would I download the zip to? I can only access the files that are on my phone through CW. I cannot or at least I do not know how to transfer files to my phone in its current state.
Thanks for the reply.
Click to expand...
Click to collapse
Do you have a spare MicroSD laying around? Use that, if your computer has an SD slot. If you don't have a MicroSD with the adapter to plug it into a normal SD slot, you can find cheap 2 GB ones with an adapter on the cheap. If your computer doesn't has an SD slot, and you have no external tools, the ADB may be able to help you, or you could find an adapter. Simply re-download the zip (or a zip for a different ROM) on the computer, and move it to the external SD. Stick said MicroSD into your phone. When you choose to install a zip in the recovery, there should be an option to choose from an external SD, if it mounted correctly.
LordDiabeetus said:
Do you have a spare MicroSD laying around? Use that, if your computer has an SD slot. If you don't have a MicroSD with the adapter to plug it into a normal SD slot, you can find cheap 2 GB ones with an adapter on the cheap. If your computer doesn't has an SD slot, and you have no external tools, the ADB may be able to help you, or you could find an adapter. Simply re-download the zip (or a zip for a different ROM) on the computer, and move it to the external SD. Stick said MicroSD into your phone. When you choose to install a zip in the recovery, there should be an option to choose from an external SD, if it mounted correctly.
Click to expand...
Click to collapse
I will try that right now, thank you!
apolanco115 said:
I will try that right now, thank you!
Click to expand...
Click to collapse
Did it work out for you?
LordDiabeetus said:
Did it work out for you?
Click to expand...
Click to collapse
I'm backing up the stuff on my SD and formatting to FAT32. It's taking a while, but It's almost done.
apolanco115 said:
I'm backing up the stuff on my SD and formatting to FAT32. It's taking a while, but It's almost done.
Click to expand...
Click to collapse
Alright. Let me know if it works for you. If reflashing the other ROM doesn't work, try another one.
Personally, I would recommend CyanogenMod 10.1.
LordDiabeetus said:
Did it work out for you?
Click to expand...
Click to collapse
When I tried this, It said
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Erro in /sdcard/SGH-T999_T999UVDLI8-OTA-T999UVALH2_TMB_341017054.zip
(Status 7)
Installation aborted.
How do I fix this?
apolanco115 said:
When I tried this, It said
file_getprop: failed to stat "/system/build.prop": No such file or directory
E: Erro in /sdcard/SGH-T999_T999UVDLI8-OTA-T999UVALH2_TMB_341017054.zip
(Status 7)
Installation aborted.
How do I fix this?
Click to expand...
Click to collapse
Seems like that certain ROM is broken. The build.prop file is missing. This is an important file, and it holds data about your phones model, ect. Try flashing a different ROM.
LordDiabeetus said:
Seems like that certain ROM is broken. The build.prop file is missing. This is an important file, and it holds data about your phones model, ect. Try flashing a different ROM.
Which is odd seeing as it is CyanogenMod. Never had a problem with it. Is this CM 10 stable, or a CM 10 nightly?
Click to expand...
Click to collapse
I was trying to install the stock firmware before now I tried a different rom, CyanogenMod 10.1 nightly, and I'm getting
assert failed: getprop("ro.product.device") =="d2tmo" || getprop("ro.build.product") == "d2tmo"
E: Error in /sdcard/cm-10.1-20121224-NIGHTLY-d2tm0.zip
(Status 7)
Installation aborted.
apolanco115 said:
I was trying to install the stock firmware before now I tried a different rom, CyanogenMod 10.1 nightly, and I'm getting
assert failed: getprop("ro.product.device") =="d2tmo" || getprop("ro.build.product") == "d2tmo"
E: Error in /sdcard/cm-10.1-20121224-NIGHTLY-d2tm0.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Uh, it seems like your build.prop is missing or corrupt.
Try using Odin again, and flash the stock from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
That's the last I can think of. Good luck.
LordDiabeetus said:
Uh, it seems like your build.prop is missing or corrupt.
Try using Odin again, and flash the stock from this thread: http://forum.xda-developers.com/showthread.php?t=1949687
That's the last I can think of. Good luck.
Click to expand...
Click to collapse
Thank you so much for your help. A website like was precisely what I spent about 3 hours looking for. I was able to flash the stock back on and now my phone boots normally thank you once again.
No problem man, glad to help! From now on, make sure you make a backup before you flash, either from recovery, or another app, or from your desktop!
Sent from my SGH-T999 using xda app-developers app
Same Exact Issue
Hey there, I'm having the same exact issue with the same phone.
I have a Galaxy S3 T999 and I'm stuck at my stuck at the Samsung start up screen. I rooted my phone today and I'm not really having trouble understanding all of this, but I am new to it.
Everything was going fine until I decided to try and install a new rom to my phone.
I installed Titanium Back-up and ROM Manager/Recovery mode (whatever it's called)
[[sorry for not being that detailed -for my situation is exactly like the one before me so I'm sparring every detail and I'd just be repeating everything above]]
After researching for hours and following every step, I ended up getting an error (the same as his) Error 7 or something like that when trying to install new rom (It was a Pac Rom version and I really expected it to work) and now the only thing I can do with my phone is go into download mode and recovery mode...
Being cautious that something like this would happen I backed up my whole phone's state with the recovery app but OF COURSE that didn't work because when I try to restore/backup, I get a md5 mismatch.... (and when I researched that, many people had the same 'mismatch error' when trying to restore last rom but the only way of fixing that is renaming and/or deleting some files in my phone -which I cannot access due to the lack of function after the start up screen...)
I really just want any rom to work at this point, I haven't been this frustrated in a long time.
I researched everything before taking every step but apparently staying up all night until 10 a.m. the next day doing what I thought was "Backing Up" my phone so nothing went wrong was a COMPLETE waste of time because EVERYTHING went wrong. :good:
Please HELP
(I don't have extra sd card, can't I just use the sd card I already have....)
Oh, and now my phone won't even turn on
it being dead is probably the most likely cause but for some reason it's not charging plugged up to my computer or wall charger....
what now????
kayrealist said:
Hey there, I'm having the same exact issue with the same phone.
I have a Galaxy S3 T999 and I'm stuck at my stuck at the Samsung start up screen. I rooted my phone today and I'm not really having trouble understanding all of this, but I am new to it.
Everything was going fine until I decided to try and install a new rom to my phone.
I installed Titanium Back-up and ROM Manager/Recovery mode (whatever it's called)
[[sorry for not being that detailed -for my situation is exactly like the one before me so I'm sparring every detail and I'd just be repeating everything above]]
After researching for hours and following every step, I ended up getting an error (the same as his) Error 7 or something like that when trying to install new rom (It was a Pac Rom version and I really expected it to work) and now the only thing I can do with my phone is go into download mode and recovery mode...
Being cautious that something like this would happen I backed up my whole phone's state with the recovery app but OF COURSE that didn't work because when I try to restore/backup, I get a md5 mismatch.... (and when I researched that, many people had the same 'mismatch error' when trying to restore last rom but the only way of fixing that is renaming and/or deleting some files in my phone -which I cannot access due to the lack of function after the start up screen...)
I really just want any rom to work at this point, I haven't been this frustrated in a long time.
I researched everything before taking every step but apparently staying up all night until 10 a.m. the next day doing what I thought was "Backing Up" my phone so nothing went wrong was a COMPLETE waste of time because EVERYTHING went wrong. :good:
Please HELP
(I don't have extra sd card, can't I just use the sd card I already have....)
Click to expand...
Click to collapse
So what I did was I used the link above your post to download a rom that I could flash with Odin and that worked. This was the link btw http://forum.xda-developers.com/showthread.php?t=1949687
Hi all, thoroughly read the guides in the T999L FAQ guide, rooted and installed CWM successfully (as far as I can see).
Now the hard part. Could not install Pacman Rom, even after fixing asserts. I heard there were two types of asserts. I deleted the ones at the top of the update-script, that look at the device number. Previously I had error 7, now I don't get an error number. Says "Installation aborted". Looking at the log, it says "Can't partition non-vfat: datamedia" and "Cant format unknown volume: /emmx"
Tried flashing CM10 for d2ltetmo and it was able to flash, except no signal/connection. Baseband displays T999LUVMB7 which is the correct one isn't it?
Preferably, I would like to flash Pacman Rom, but as I cannot get it to work as hard as I've searched and tinkered, I would settle for just any working ROM right now. I've been without a phone for a few days now before receiving this one today, and I really need to get it to work.\
Kinda wish my T999 wasn't replaced with T999L... all this seems too complicated than what I want to get into right now, with modems and bootloaders (never had to touch that on my T999) etc. I'm just confusing myself and at this point I've decided to ask the board instead of risking damaging anything.
Hi all -
I've tried researching this but can't find a solution that works; I've looked on XDA, OnePlus' own forums, general Google search, nothing seems to work or fit.
I tried backing up my Nougat Open Beta 11 build today, and all of a sudden I'm getting an error message in TWRP 3.0.3.0 :
createTarFork ( ) process ended with ERROR: 255
It aborts the backup attempt at that point. I've tried flashing older versions of TWRP, but that didn't help. I've tried not compressing the backup, that didn't help. Some people on other forums said deleting addon.d from /system was the cure, but I don't have that file.
Recovery.log is attached, if anyone has a suggestion or can point me in the right direction, I'd greatly appreciate it. Others have said doing a complete wipe/clean install fixed things, but I'd rather not go with the nuclear option if I don't have to. Thanks! :laugh:
With Nougat use Unreleased TWRP v3.0.4-1
Link to TWRP v3.0.4-1 thread: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
I use 3.0.3 x v.15 blu spark. Works fine.
Dear XDA-Developers,
After trying for many hours searching different forums and websites looking for help, I decided to make an account here and ask for help here.
I am currently on a Rooted OnePlus 5t with OxygenOs 9.0.3. I have not updated my phone in a really long time and decided to do so now.
I decided to dirty flash the full official ROM for OxygenOs 9.0.11 which was released recently with TWRP.
At first, I was on an older version of Blu_sparks recovery but replaced it with the newest TWRP from their website (Dumpling 3.3.1-0).
When I first tried to flash it, I got this error message:
failed: no space left on device
E1001: failed to update system image.
Updater process ended with ERROR 7:
Error installing zip file 'sdcard/download/Oneplus5Toxygen_43_OTA_054...
After trying multiple other recoveries, trying to flash with and without the compatibility zip and also trying to flash earlier versions of OxygenOS with different TWRP versions, I still get the same error message from TWRP as above.
Since it says that I supposedly don’t have enough free space, I looked for a way to change that and came across a thread which suggested to free some space by removing system apps that are not unnecessary, I tried doing that and flashing it again, but that also wasn’t successful.
My phone also has more than 10gb of free space.
I also tried to change the „assert“ line in the updater-script of the update, but I did not find any such line in the updater-script document in the zip file?
Does anyone know what causes this error message and what I can do to successfully update my phone?
And I was also wondering what would happen if I just let my phone regularly update it over settings?
It says that root is detected and my phone would be un-rooted once the after updating.
However, the update shown is only 1839mb so I’m very hesitant to do it.
But if I went through with this, would I just have to reroot my phone?
Will my recovery be replaced with the stock recovery, or will it remain TWRP?
Will my Bootloader get locked again?
Thank you so much for taking the time to read this, I appreciate it.
With kind regards,
Mutambo23