Related
Last night, I decided to try out the Trinity kernel. I downloaded and flashed, and everything went without error. After that, I pushed a custom boot animation over ADB. The first one didn't work, and after the splash screen disappeared it was simply a black screen, but then I pushed one I downloaded from XDA and it was fine.
Now, though, I want to make a nandroid, but CWM is running into some issues. I started the ROM manager app, entered a name for the nandroid as usual, and hit OK, but when it rebooted into nandroid, it gave me an error saying "Error mounting /system" and rebooted back into CM7. That's odd, I thought, I never had any problems like that before. So I rebooted into CWM myself by holding down power+vol down and tried making a nandroid there. No luck. Then I went to mounts and storage and tried to manually mount /system. CWM gave me the error again.
I'm not really sure what's causing this. I thought it might be because now I'm using an ext4 filesystem because of Trinity (right? haha I'm new to kernels and such) and CWM might not support reading it, but if that's the case, I think I would not be the first to have this issue. Yet I searched, on that thread, on Google, on XDA general search, and didn't see anything. I also doubt it's the boot animation.
My last nandroid was yesterday. The only changes to the system I remember right now is that I flashed CM7 nightly 101, then flashed Trinity, rebooted, and flashed the boot animation mentioned. I installed apps since then but none of them had root so I doubt that's it. I would reflash CM7 to overwrite Trinity, but I read on the Trinity thread that if I did that without restoring an old CM7 kernel nandroid first, I'd be stuck in a bootloop because of ext4...?
So, what should I do? I don't want to make anything worse than it already is by tinkering with this myself, I no longer have a current nandroid, that's why I'm asking XDA. Does anyone have an idea why this might be happening? I'm sorry if a thread like this already exists or if this is in the wrong forum (if so mods please move it), this is my first time posting and my search skills could suck (although I looked in all the places I could think of)
Thanks for your help! My G2x is running CM7 nightly 101. Both the nvflashed CWM in recovery and the CWM started by the rom manager app are version 3.0.2.7.
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
ritthyhang said:
I got the same problem as you bro right after flashing trinity
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Good, so I'm not the only one! I thought that was too odd to be true.
Here's what I've done. I reflashed cm7 nightly 101 to get my CM kernel back and rebooted. Sure enough, bootloop. Or it never got past the splash screen to the CM7 android skateboard boot animation. I went back in recovery, though, and was able to mount /system. Odd. So I flashed trinity again and tried mounting /system again and no go. So this definitely has something to do with Trinity... I restored my nandroid, reflashed 101,and that's where I am now. Tomorrow, I will make an up-to-date nandroid and do some tinkering to try to figure out what's going on. Maybe it has something to do with the boot animation, maybe not, exactly what's going on is what I am going to try to figure out if no dev shows up here.
Could you give me a few details about your case? Were you coming from cm7 too? Did you do any boot animation tinkering like me?
Sent from my LG-P999 using XDA App
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
ritthyhang said:
Okay so I was eaglesblood 1.6 and flashed trinity the other day. Before trinity I was on miui and made plenty of nandroid backup. So today and 1.7 got released so before update I try to backup then behold Our Problem. So after I confirm that I can flash 1.7 over 1.6 I decided to take that risk and flashed anyways. On 1.7 the Superuser was updated I notice, so I decided to make a backup and it Work. So I think the problem was had to do with the outdated Superuser. I think I might be wrong that's just my experience.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Hmm. So to clarify: You were running MIUI, then you flashed eb followed by trinity. Then, eb 1.7 was released and you went to nandroid, but you couldn't mount /system, so you took the risk and upgraded anyways. The new be came with a new version of superuser, and you were able to make nandroids once again. Is this correct?
One very important question if it is. Did you flash trinity again after flashing the eb 1.7 update?
Also, could I ask what version of superuser came in this update? I am using version 2.3.6.3, which is the latest according to Superuser check for updates, but ROM Manager lists a 3.0 beta version and I'm wondering if you're using that. To check, open Superuser, go to the settings tab, and scroll all the way down. It's the second to last option for me. It's unlikely that superuser is making the difference, since it works as a part of Android and our problem is in recovery, before Android loads, but I can see how it might be possible. If you're using the 3.0 beta, I will flash to that and see if it fixes.
I will look into this some more tomorrow, specifically right now I want to know what filesystem eb's kernel recommends.
Sent from my LG-P999 using XDA App
G2X here same problem.
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
Update cwm to latest recovery 5.0.2.0 i believe.
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
lithivm said:
I think they key here is MIUI. I tried to load MIUI image and it didnt go well. I formatted and CWR to restore and its been giving me issues same cant mount system errors.
Right now I downloaded CM7 and installed it from scratch and I can use the phone but it wont backup my ROMs anymore.
Have you guys found anything new ?
Click to expand...
Click to collapse
I just stopped using Trinity and went back to the stock CM kernel. I don't think it's just miui, I never used that. But...
fcisco13 said:
Update cwm to latest recovery 5.0.2.0 i believe.
Click to expand...
Click to collapse
squish099 said:
+1 cwmr 5.0.2 is the first to officially support ext4 partitions
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
YESS! Looks good. I did hear about that. Looks like it's time to give Trinity another try
Error mount/system!
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
Update your recovery, both, fake and nvflash.
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
jblah said:
i was also having the can't load system issue. upgrading to latest clockwork mod via rom manager to v5.0.2.0 resolved the issue and i was able to take a backup of my current system.
Click to expand...
Click to collapse
Where do I find the latest clockwork mod and how do I install it? I currently have a soft bricked phone, and I can't seem to get it unbricked. I tried using the pit files with the stock rom, the dbdata stuff and everything else. What happened was the the system was in ICS, but something happened and I couldn't load into CWM 4 and the system wouldn't boot. So to fix, I used odin to install the stock rom (v2.3.3), but the stock rom came with CWM 3.0, so now I'm at 3.0 and can't mount the file system and it's not booting. I'm assuming that if I upgraded the CWM back to a newer version, I'll be able to restore the system and gain access to the file system again.
reboot problem
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Abizer98 said:
i jus flashed ext4 converter for kernel update every think went fine but i couldnt mount system coz it was showing error i neglected dat nd flashed every thing was done nd when i rebooted it gt stuck in d samsung galaxy y logo...plzzz help meee wat to do..plzzz help
Click to expand...
Click to collapse
I'd ask in the samung galaxy forums bud.
"my mind draws lots of blanks actually"
Solution
asn_86 said:
I can't restore my stock rom,i've tried to fully wipe but got:
-- Wiping data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
and cant restore
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Error mounting /system!
Skipping format
Can't mount /system!
and cm7 doesnt boot,now im just stuck in ClockworkMod Recovery v4.0.0.5
is there any ways to flash stock rom in clockworkmod??
Click to expand...
Click to collapse
actually yes. the /system folder is corrupt and it need to be formatted. so all you need to do is format / system then it will work as it should
hope that helps
I am using Smil bean 3.1 based on CM 10 Alpha 4, Kernel- 2.6.35.7. after installing is i've replaced the file /system/build.prop after seeing the post -
http://forum.xda-developers.com/showthread.php?t=1933837.
After that I have lost the Exchange, after rebooting need a lot of time to get the network signal, sometime got black booting screen. But the main prob is i can't flash any other rom. Tried few time properly (resetting user data, formatting cash, formate dlvk cash. after installing is shows E:unknown volume/cash not found or cash no mount, no log ect and came back to old Slimbean,
Sow can i replace the old Build.prop?
AnYOne Help??
ghunpoka said:
I am using Smil bean 3.1 based on CM 10 Alpha 4, Kernel- 2.6.35.7. after installing is i've replaced the file /system/build.prop after seeing the post -
http://forum.xda-developers.com/showthread.php?t=1933837.
After that I have lost the Exchange, after rebooting need a lot of time to get the network signal, sometime got black booting screen. But the main prob is i can't flash any other rom. Tried few time properly (resetting user data, formatting cash, formate dlvk cash. after installing is shows E:unknown volume/cash not found or cash no mount, no log ect and came back to old Slimbean,
Sow can i replace the old Build.prop?
AnYOne Help??
Click to expand...
Click to collapse
From the main page of CM10 Alpha 4..if you have spent time reading it...
IMPORTANT! READ BEFORE FLASHING THIS RELEASE!
2. Once on this ROM, the most effective way of going back to any other ROM would be to repartition from Odin.
If you did not keep a copy of the original build.prop before you replaced it, you got nothing to go back to
yeah, the best way is to repartition and flash back to stock rom. after that, flash cfroot and then cm10 a4 first. when you have finished flashing cm10 a4, that is the time you can flash other roms based on cm10. hope i helped.
imboy25 said:
yeah, the best way is to repartition and flash back to stock rom. after that, flash cfroot and then cm10 a4 first. when you have finished flashing cm10 a4, that is the time you can flash other roms based on cm10. hope i helped.
Click to expand...
Click to collapse
I have been trying to re-partition by Odin and go back to stock rom 2.3.6 DDLF, but Odin can't re-partition it. 1st time it flashed the stock rom but stacked on boot loop. I've even tried to data reset on recovery mood but its show- "E: format_volume: rfs format failed on /dev /block / stl10
Could not understand what to do
ghunpoka said:
I have been trying to re-partition by Odin and go back to stock rom 2.3.6 DDLF, but Odin can't re-partition it. 1st time it flashed the stock rom but stacked on boot loop. I've even tried to data reset on recovery mood but its show- "E: format_volume: rfs format failed on /dev /block / stl10
Could not understand what to do
Click to expand...
Click to collapse
Have you tried flashing first KPE stock rom (with pit, pda, modem, csc files)? If not, try flashing it first and then upgrade to LF2.
Sent from my GT-I9003 using xda app-developers app
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
bweN diorD said:
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
Click to expand...
Click to collapse
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
ajh305 said:
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
Click to expand...
Click to collapse
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
bjoostema said:
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
Click to expand...
Click to collapse
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
EDIT: I tried another 4.3 rom and booted it up. Set some things up then updated su binaries and restarted and let it sit there at the unlocked bootloader warning for 15 minutes with no changes.
bweN diorD said:
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
Click to expand...
Click to collapse
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
ajh305 said:
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
Click to expand...
Click to collapse
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
bjoostema said:
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
Click to expand...
Click to collapse
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
ajh305 said:
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
bjoostema said:
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
Click to expand...
Click to collapse
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
ajh305 said:
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
Click to expand...
Click to collapse
Awesome man! I'm glad it booted up for you welcome to the 4.3 side!
ajh305 said:
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
Click to expand...
Click to collapse
glad you got it fixed but i have to ask, in the sequence above why are you restoring a backup? you should be going right from stock to 4.3. also, some people have issues with twrp and 4.3, thats why i suggested cwm.
I'm not sure why I restored the backup. I didn't think coming from stock would work for some reason.
Sent from my XT926 using xda app-developers app
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
sgtslaughter64 said:
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
Click to expand...
Click to collapse
This was the only thing that worked for me. You could maybe try updating to the most current recovery instead of the one listed.
the only 2 issues i have seen to cause this problem are covered in the post a few below, and fixed it every time. my only suggestion would be to install cwm after rooting, then reboot, then continue with the steps. just my preference, it may not matter.
Hi There,
So, I have a Samsung Galax S2 Telus SGH-T989D phone and I decided to root it using the 4.4 KitKat and it went well and everything was great.
However, afterwards to resolve some other issues I was having I decided to make the mistake of loading the gapps which was for another
package into my phone and that messed everything up!
So, I have been struggling with the phone and first it wouldn't let me install another ROM from recovery and kept on giving me error 7 and 6
But, I fixed that and now I can install any ROM from the recovery or Odin (download mode) without any errors.
However:
The phone vibrates , brings up the galaxy logo and then the Koodo logo appears and a bar fills up quickly under it but it never goes away!!!
Phone freezes there and that's that!! Even after taking out the battery I noticed the logo was still stuck on the screen where as normally
it goes blank!!
So, at this point I am not sure what else to do! This is annoying and I'm tired of experimenting. I went through some XDA foroums here and
tried the Super Vipe (taking out the battery has been tried, factory reset and wiping the cache all have been tried)
So, please please please help me out here. I used to have a MyTouch4G which I rooted with CyanogenMod back in the day and it's the most
stable thing ever and all I wanted to do was to perform the same thing on my Galaxy S2 and boom not this time!!!
Awaiting your response and thanks in advance
King-2012 said:
Hi There,
So, I have a Samsung Galax S2 Telus SGH-T989D phone and I decided to root it using the 4.4 KitKat and it went well and everything was great.
However, afterwards to resolve some other issues I was having I decided to make the mistake of loading the gapps which was for another
package into my phone and that messed everything up!
So, I have been struggling with the phone and first it wouldn't let me install another ROM from recovery and kept on giving me error 7 and 6
But, I fixed that and now I can install any ROM from the recovery or Odin (download mode) without any errors.
However:
The phone vibrates , brings up the galaxy logo and then the Koodo logo appears and a bar fills up quickly under it but it never goes away!!!
Phone freezes there and that's that!! Even after taking out the battery I noticed the logo was still stuck on the screen where as normally
it goes blank!!
So, at this point I am not sure what else to do! This is annoying and I'm tired of experimenting. I went through some XDA foroums here and
tried the Super Vipe (taking out the battery has been tried, factory reset and wiping the cache all have been tried)
So, please please please help me out here. I used to have a MyTouch4G which I rooted with CyanogenMod back in the day and it's the most
stable thing ever and all I wanted to do was to perform the same thing on my Galaxy S2 and boom not this time!!!
Awaiting your response and thanks in advance
Click to expand...
Click to collapse
Clean solution: Flash stock firmware via Odin or install custom rom via recovery
LS.xD said:
Clean solution: Flash stock firmware via Odin or install custom rom via recovery
Click to expand...
Click to collapse
Thank you for your reply. However, as I've mentioned before, I've already tried those (from ODIN and through RECOVERY) with multiple different
ROMS and it's not doing anything which is why I am posting this here.
King-2012 said:
Thank you for your reply. However, as I've mentioned before, I've already tried those (from ODIN and through RECOVERY) with multiple different
ROMS and it's not doing anything which is why I am posting this here.
Click to expand...
Click to collapse
Did you perform a FULL wipe? Custom recovery -> format ALL partitions except EFS?
I have tried the Super Vipe off the SD card through the recovery mode and also from recovery I've tried the wipe cache,
factory reset and wipe cache partitions.
I am not sure about "format ALL partitions except EFS" nor am I aware of the procedure.
How would I perform that?
Have you installed a working custom recovery?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Have you installed a working custom recovery?
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Yes I'm able to successfully install recovery-clockwork-5.0.2.7-hercules or CWM_Root_Superuser_3.1.3_Busybox_1.20.2
from the recovery without any errors (same if rooted through Odin)
If there's a specific ROM you are thinking about please let me know and I will be more than glad to give it a shot.
You really should use a newer recovery version. But for now go to mounts and storage and format all partitions except EFS. Then try flashing stock firmware via Odin
Here you can get the latest recovery for your device --> TWRP for hercules
LS.xD said:
You really should use a newer recovery version. But for now go to mounts and storage and format all partitions except EFS. Then try flashing stock firmware via Odin
Here you can get the latest recovery for your device --> TWRP for hercules
Click to expand...
Click to collapse
Under mounts and storage and format all partitions except EFS > Don't even see ESF there to begin with..
Do you have a working link for downloading the stock firmware? I have downloaded few and none of them even let me install them (status 0 error)
Any ideas?
Odin is already being used v3.0.7
Format System Data Cache dalvik. Realy... Then flash stock firmware using ODIN!
Sent from my beloved HTC One S using (most time buggy) Tapatalk
LS.xD said:
Format System Data Cache dalvik. Realy... Then flash stock firmware using ODIN!
Sent from my beloved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
I was able to finally bring it up!!
Basically I looked for a stock firmware for T-Mobile and after formatting the phones multiple times I tried this ROM
using ODIN and it got rid of the Koodo logo and replaced it with a T-Mobile logo and then it BOOM loaded to start screen finally!! :laugh:
I was about to hammer the phone. So, trust me I was very happy to see it work.
Thank you for your quick and helpful response :good:
Cheers :victory:
Hi ,guys .
So my problem is the first boot (on my p3110 )takes an eternity , whatever I'm trying to flash it wouldn't succesfully have the first boot .
I've tried omni,slimkat and CM but nothing works .
Dumb I was ,in my blind tries, I've deleted my backups and now the only place i can flash is my microSD card.
Help please , I'm really stuck . :crying:
TheHelplessGuy said:
Hi ,guys .
So my problem is the first boot (on my p3110 )takes an eternity , whatever I'm trying to flash it wouldn't succesfully have the first boot .
I've tried omni,slimkat and CM but nothing works .
Dumb I was ,in my blind tries, I've deleted my backups and now the only place i can flash is my microSD card.
Help please , I'm really stuck . :crying:
Click to expand...
Click to collapse
The first boot always takes longer as it is setting up, but no longer than ~5 minutes.
Anyway... If you've waited and it is boot looping, try these steps:
Make sure your recovery is up to date.
Wipe system, data, cache, and dalvik cache.
Flash ROM, gapps, and any addons
Wipe cache and dalvik
Reboot. After first reboot is complete and on setup screen, wait 5 minutes and reboot into recovery.
Wipe cache and dalvik again. Reboot
This reboot could also take ~5 minutes, but the others shouldn't as long as you don't wipe cache and dalvik.
You should see an "Android is Upgrading" screen. After this is done, complete setup and you should be good to go.
Sent from my SGH-T989
The same
jrc2 said:
The first boot always takes longer as it is setting up, but no longer than ~5 minutes.
Anyway... If you've waited and it is boot looping, try these steps:
Make sure your recovery is up to date.
Wipe system, data, cache, and dalvik cache.
Flash ROM, gapps, and any addons
Wipe cache and dalvik
Reboot. After first reboot is complete and on setup screen, wait 5 minutes and reboot into recovery.
Wipe cache and dalvik again. Reboot
This reboot could also take ~5 minutes, but the others shouldn't as long as you don't wipe cache and dalvik.
You should see an "Android is Upgrading" screen. After this is done, complete setup and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
The same loading image .(You know ,when you first boot something it appears the custom flash's logo) . what can i do ?
TheHelplessGuy said:
The same loading image .(You know ,when you first boot something it appears the custom flash's logo) . what can i do ?
Click to expand...
Click to collapse
How long have you tried waiting? Which room door you flash on which device?
Sent from my SGH-T989
jrc2 said:
How long have you tried waiting? Which room door you flash on which device?
Sent from my SGH-T989
Click to expand...
Click to collapse
I've waited more than usual 5-10 mins ,even 6 hours ,but nothing, ,I'm curently trying to flash slimkat 4.4.4 but i've tried omni ,CM all kitkat .
What is your advice ?
TheHelplessGuy said:
I've waited more than usual 5-10 mins ,even 6 hours ,but nothing, ,I'm curently trying to flash slimkat 4.4.4 but i've tried omni ,CM all kitkat .
What is your advice ?
Click to expand...
Click to collapse
What version of unroofed TouchWiz were you running before rooting and flashing?
Sent from my SGH-T989
jrc2 said:
What version of unroofed TouchWiz were you running before rooting and flashing?
Sent from my SGH-T989
Click to expand...
Click to collapse
The one with Android 4.1 my guess is Nature UX
TheHelplessGuy said:
The one with Android 4.1 my guess is Nature UX
Click to expand...
Click to collapse
Then idk what the problem is. You were on jelly bean already so that isn't a problem.
Sent from my SGH-T989
jrc2 said:
Then idk what the problem is. You were on jelly bean already so that isn't a problem.
Sent from my SGH-T989
Click to expand...
Click to collapse
What do you suggest ?
TheHelplessGuy said:
What do you suggest ?
Click to expand...
Click to collapse
I don't know, sadly. Maybe someone else will know and we'll both learn something.
Sent from my SGH-T989
Back to stock rom for now, prepare (charge until full).
Re-root, then reboot to recovery to try again flashing the rom.
Always format /system, /cache, /data/media first when installing different roms. Good luck
150208 said:
Back to stock rom for now, prepare (charge until full).
Re-root, then reboot to recovery to try again flashing the rom.
Always format /system, /cache, /data/media first when installing different roms. Good luck
Click to expand...
Click to collapse
I did exactly as you said but nothing happened .
1. It's a problem that i install zips from my external storage ?
2.Do you know where i can find a nandroid backup to download ?
3.What do you suggest for my issue ?
TheHelplessGuy said:
I did exactly as you said but nothing happened .
1. It's a problem that i install zips from my external storage ?
2.Do you know where i can find a nandroid backup to download ?
3.What do you suggest for my issue ?
Click to expand...
Click to collapse
Stock rom is working fine? Is root working on stock?
Did you get any errors while flashing costom roms?
I remember a folk here got a same problem as you, and i think it's not resolved yet..
Maybe you and him have a "special" devices.
Don't worry, it's not a problem with your ext-sd because i use it all the time. and if it was ext-sd problem, you'll get an error while flashing.
I suggest messages devs in developement section, maybe they can figure out what is wrong.
And of course i think it's not safe to restore others nandroid backup, so don't mind find it.
God speed, wish I can help you more :angel:
150208 said:
Stock rom is working fine? Is root working on stock?
Did you get any errors while flashing costom roms?
I remember a folk here got a same problem as you, and i think it's not resolved yet..
Maybe you and him have a "special" devices.
Don't worry, it's not a problem with your ext-sd because i use it all the time. and if it was ext-sd problem, you'll get an error while flashing.
I suggest messages devs in developement section, maybe they can figure out what is wrong.
And of course i think it's not safe to restore others nandroid backup, so don't mind find it.
God speed, wish I can help you more :angel:
Click to expand...
Click to collapse
Sadly my stock rom is gone.
So yesterday when I've rerooted whit your link I've received two errors :
- SOKP and when I've flash it something like poped up : E:Cannot write to sd card clockworkmod recovery etc.
- CM 11 :
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
TheHelplessGuy said:
Sadly my stock rom is gone.
So yesterday when I've rerooted whit your link I've received two errors :
- SOKP and when I've flash it something like poped up : E:Cannot write to sd card clockworkmod recovery etc.
- CM 11 :
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
Click to expand...
Click to collapse
Like I said earlier, you should have flashing stock rom first to remove root via odin/hemidall.. you can find it at sammobile,com
then re-root with link i gave earlier again via odin/hemidall, and format in recovery like i said earlier. no wonder you still fail..
you should have philz touch recovery instead cwm if you succeed.
150208 said:
Like I said earlier, you should have flashing stock rom first to remove root via odin/hemidall.. you can find it at sammobile,com
then re-root with link i gave earlier again via odin/hemidall, and format in recovery like i said earlier. no wonder you still fail..
you should have philz touch recovery instead cwm if you succeed.
Click to expand...
Click to collapse
re-rooted as you said still the same loading screen , you can give me a link to the part of the forum where I can speak with developers as you said few comments ago