Database Users

loaded wrong rom, stuck on boot screen

Apologies for this stupid question resulting from a stupid mistake. Hoping somebody will be able to walk me through getting out of this.
I successfully rooted my sprint hero, then loaded modaco 3.0 (yes now I know that was bad). On reboot, the phone hangs on the black htc screen, and will respond to nothing.
The only thing I've been able to do is remove the battery, then turn it on in recovery mode. There, I did a wipe data/restore factory setting. Then I rebooted - and got the same boot screen, same problem.
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
When I try to restore, I get these:
(bart) error: run bart via adb
(nandroid) can't open file
Please help! I am out of ideas. Thanks very much in advance.

you'll probably have to take it back to the very beginning......
Get the Sprint RUU stock rom (a couple of posts below this one) and run that
then re-root your hero
Flash one of the roms ON THIS BOARD ONLY!!! Any other Hero rom is meant for the GSM version so it will give you the same headache again.

thanks
Thanks for the quick response! I'll try that.

Hmm, not looking good here. When I tried to install the stock hero RUU I got this error:
no signature
verification failed
which I presume is related to the htc sync requirement for that rom in the unrooting procedure that I did earlier.
Any idea for working around that?

So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.

david.danaan said:
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
Click to expand...
Click to collapse
Don't use 1.1, grab a later one.
Which recovery? 1.5.x won't let you go back to the main menu without disabling USB-MS again... I don't remember what 1.2.3 did. If worse comes to worst, reboot the phone after copying the file.

gu1dry said:
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
Click to expand...
Click to collapse
Yes, that's the one.
Using recovery 1.5.1. I can try a later rom, see if that works. I think I downloaded 1.3.

So first off yes, you aren't booting past the HTC screen because you flashed the wrong rom. However you aren't bricked. It's almost impossible to do once you're rooted and have RA's recovery installed unless you flash radios and stuff which you shouldn't.
Explanations for your other problems:
1. RUU doesn't work on the phones that are coming from the factory with 1.56. http://geekfor.me/news/sprint-ruu-fails/
There is a possible work-around but it's pretty detailed and I haven't gotten it to work. But you don't need to RUU if you can get in to RA.
2) (nandroid) can't open file is likely caused by RA 1.5.1. It had a bug that corrupted the backups. 1.5.2 is out. But for now don't worry about that cause your backup already sounds corrupted, nothing you can do.
3) can't open /sdcard/update.zip (bad). To me that sounds like your update was just corrupted.
How to fix it:
1. Boot in to recovery. With phone powered off hold your home button and then power.
2. Download fresh rom from http://geekfor.me/new-release/fresh-rom-1-0/ (what can I say... I'm partial. )
3. Within RA enable USB toggle and copy fresh rom to the root of your sdcard. Don't worry about renaming it to update.zip
4. Disable usb toggle. Go to flash zip from SD and choose fresh. That should be it. If you get the error saying the zip is bad then compare your downloaded copy with the md5 hash check on the download page (google it if you aren't sure how). If it matches then it's possible you have a bad sdcard. If it doesn't match then your downloads are crappy.

working!
Got it working by flashing the modaco v1.3a - must have been a bad update.zip before like you said. Thank you so much for the help and clear explanations, I was really worried I had bricked it.

David, now that it is working, I would recommend updating your recovery to 1.5.2.

I just want to thank everyone that posted to this reply I honestly thought that I bricked my phone and thank to you guys I was able to revive it. Thank you again.

Have to admit I need some help with rooting

Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.

This means you are on the leaked version now and there is nothing that can be done as of right now.

K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?

ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.

sounds like you got a bad pb001.img file.

ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?

nevermind addressed my issue

As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5

ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.

af man...seriously!

out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"

HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA

ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!

[Q] current rooting/2.3 instructions

As the thread title states, I'm looking for info on the steps to root my stock MT4g, and install the new ROM that's floating around. I'm pretty technically capable, but the info I've found looks slightly dated. When I was active in the iPhone jailbreak scene, using old directions could brick a phone pretty easy, or prevent future jailbreaking. I haven't kept up with this scene enough to be able to know what's dated and what isn't.
This is my current plan, please correct it if I'm missing anything or have it wrong.
(based on wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide)
I've got ADB going
I need a backup solution for app data right? What's my best option here?
Once backed up, I plan to install busybox, Superuser package & Temporary Root package via ADB
Use gfree to make that root permanent
Install ClockworkMod recovery
Reboot into recovery, and install faux123's ROM
Does that sound correct, and did I skip anything? Any input at all is welcome, I'd like to stand tall on the backs of giants.

There are two popular methods floating around
You can either use the Root.sh method [ Found Here ]
Or the ./gfree method [ Found here ]
Either method will work perfectly. I've used both and can say with confidence they work.
The Cyanogen method can be goofy at times. I've see alot of people say they cannot get it working for them. I'd rock one of the two above. You shouldn't have a problem either way.

Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?

lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
For backing up apps and data, use titanium backup. for backing up your whole phone, use the backup feature in clockworkmod recovery after you've flashed it via rom manager after permarooting.

lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
The best way to back up your Data and Applications is like mentioned above is Titanium Backup. The free version will work well but i recommend the paid one.
as far as a snap shot of the entire ROM incase you want to go back to it. reboot into recovery > backup/restore > backup. And it will do the rest.

Well I made it halfway there, but didn't nail the whole thing. I've got permanent root access (yay) now, and was able to make backups via Titanium. I then rebooted the phone into "recovery" using the ROM Manager from Clockwork. First boot had a red exclamation mark, I unplugged the handset from the USB and tried a second time. After that, I was greeted with the Orange and black interface, and selected "restore to factory". I then started searching for the cache clearing, which changed verbage between 3.x and 4.x releases of Clockwork. After exploring the menus a little, the phone reboots itself from this screen. My blood-pressure goes up, and I worry my toy just became a b-word. Not all was lost though, and the phone happily booted into the stock t-mobile welcome wizard.
I still have superUser installed, and still have root (S=OFF I guess?). I install ROM Manager again, and do the "Flash ClockworkMod Recovery" (which now shows both current and latest recovery as ClockworkMod 3.0.2.4). When I choose Reboot into Recovery however, it reboots back to the MyTouch 4G logo screen (non-animated one), and hangs. After some reading I tried to force recovery boot via ADB, which produced the same result as the soft reset from ROM Manager. After that I tried doing it the manual way with holding the volume button, which launched me into what I believe is a stock recovery console (white with colored options, uses vol +/- and power to navigate). Choosing "recovery" from that screen *also* produces the white logo screen hang.
So my question now is, in it's current state; how can I get to the Clockwork recovery again? From there I bet installing the image will be easy street, but I believe I'm stuck for now.
Side-note: the phone functions fine on regular boots and pure vanilla mode; I just don't want to stop here when I'm pretty close to my 2.3 goal

Well good news and bad news. I was able to get Clockwork going by reverting it to 3.0.0.5 and just using that version. Was able to install ROMs, tested a few. Phone started freezing after/during installing packages. Started the clear cache/install ROM process, ran into this:
Code:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
http://forum.xda-developers.com/showthread.php?p=14389074
Totally stuck at boot screen, but able to get into Clockwork. All ROM zips off the sdcard produce this or an invalid zip error.

Other guy smight tell you what a status 7 might be, but with the flurry of flashing youre doing, you may have gotten some corruption on your sd
try formatting your sd card in the pc, or use another one so you dont have to back everything up on this one. put one rom zip on the root and see if that helps
also, i would make super sure you wiped/factory resetted every possible data/cache in CWM before flashing the zip
lastly, i would md5 test the download to make sure it matches the web page. Plus, after it's transferred to the cleanly-formetted sd, check it again either thru adb, or do the trans on the pc using an sdcard reader and check it once it's on the sdcard, then pop it into back your phone.
good luck

Thanks a ton for the uber fast reply. When I format on the PC, what format do I use, or is there a specific tool to properly format it for the phone?
When I'm wiping /data it's taking forever and I get the following message back:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log/last_log
E:Can't open /cache/recovery/log/last_log
Don't have an adapter at the office today for the sdcard, but I guess I can just grab a new one at lunch? All it would need is a fresh format then the .zip of the ROM in question at the root?

Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.

Jack_R1 said:
Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.
Click to expand...
Click to collapse
So I use the same PD15IMG.zip i did to start, flash it using Clockwork, then start the root > rom process over? I think that it currently tells me it can't find that zip anymore on the white screen pre console, is that expected? I just xfer it to the sdcard prior to fixing?

Yes, that's the right procedure. Move it to the card and start from scratch. Beware not to use the newer Panache/MT4G Gingerbread RUU, otherwise you'll be left with no way to root, or at least harder way.

Ok, so I didn't have a PD15IMG.zip to begin with, I see this thread:
http://forum.xda-developers.com/showthread.php?t=1059347
and that's proper that I'm flashing the radio itself for this process? Which of those images do I want to grab? I always like to double check when I read warnings that are pretty specific about bricking the device

No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.

acsi007 said:
No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.
Click to expand...
Click to collapse
Jesus, glad I asked before getting in there.
So I was going to offer you a beer sometime, I think I owe you a few rounds at this point...
Edit: this one right http://forum.xda-developers.com/showthread.php?t=924923 ?

Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...

acsi007 said:
Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...
Click to expand...
Click to collapse
I rooted gfree originally, and think I may be in the bad place
Fail-PU errors running the update from pd15img. Do I have any options at this point? I bought the phone from Wirefly.com, and since I can't get a recovery image going, I may be fuct here on a return eh?

looks like i'm moving to: http://forum.xda-developers.com/showthread.php?p=14487111#post14487111

Good luck Lars. Let us know that they did and if you had to pay.

[Q] EMERGENCY - Lost kernel and rom, can I recover?

So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!

DreadyBear said:
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
Click to expand...
Click to collapse
How did you tried connecting phone to odin? Did you went into download mode then connected the phone to pc ?

DreadyBear said:
So super sorry for this one, but 9 hours of trying has left me no choice but to beg for help and I am running out of time to search for the solution.
Ok, I have softbricked my s5360B, foolishly I didn't make a rom and/or kernel backup before I tried messing around with my phone, I was trying to simply network unlock my device, I return back to the UK from Brasil on Saturday and I need an operational phone so I can get home.
I settled on using JellyBlast rom for my installation but after running into installation errors like (status 7) and later on a (status 0) I got frustrated and tried installing any of the .zip files (JVBota1signed.zip and filetypes similar to). And I think I messed up badly - the phone when booting has the original 'samsung galaxy y s5360b' screen but does not move past it, at one point it flicked back an to from this splash screen and Vivo (brasil network carrier) but now it does not. I still can boot into CWM recovery (v6.0.4.9) which is a good sign I think.
As a mac user I am a little adversed to using Odin - Windows 7 via Parallels recognizes the phone and begins installation of stuff, but hangs up at 'setup connection', so I think I need a solution that I can use just the SD card for. I need a fix as quick as possible - I have only 2 days left here and during that time I have to say my forever goodbyes to my love.
Bottom line - I need my phone operational ASAP - I don't care about what version of rom or kernel it is running (be it factory stock or custom), just so long as I can be network/carrier unlocked. If you have a viable solution for me can you please post links to downloads for the files I need? And if there is any more complexity than 'install this then this' then I may struggle. What do I do?
Really appreciate the efforts of the community, thanks guys!
Click to expand...
Click to collapse
The rom you mentioned is a banned rom
You have 2 options
Option 1
If you can get into recovery mode (Vol up home button power button)
Download any stock based custom rom
Go into cwm
Format system data cache
Mount system data cache
Flash rom zip
Assuming that you are using a stock based kernel it will boot
Option 2
Flash stock rom via odin
See my firmware thread link in my signature
Note you can use standard 5360 firmware instead of the b variant which may be better

Posting to say I didn't get the phone to work still, but I got home without too much trouble. needless to say this thread is no longer an emergency.
I want to express my gratitude to you guys for helping me out, thank you so very much.
Unfortunately as I say the phone does still not work -
With multiple attempts using ODIN I keep getting the hangup at 'setup connection' - I tried on mac via parallels (windows 7) and a windows 8 machine.
I can successfully install a ROM via CWM but the phone gets stuck in a boot loop (samsung galaxy y splash screen) so I'm guessing I have a kernel problem? When I try flashing a new kernel I get the "error mounting /sd-ext!" message, and the same when I try to format it via CWM. I found this: http://forum.xda-developers.com/showthread.php?t=1750888, but I cannot boot the phone so I guess I'm stuck.
My last install attempt was these
http://forum.xda-developers.com/showthread.php?t=2462914 - V3LenoxEvolution ---- SUCCESSFUL INSTALL.
http://forum.xda-developers.com/showthread.php?t=2644262 - Blackheart kernel ---- FAILED, error mounting /sd-ext
Got any other ideas guys? Or do you know where I'm going wrong?
I think I'm in way over my head :s
Many thanks once again!
EDIT: some additional information, I cannot reboot to bootloader, and as far as I can tell I can't replace the custom recovery CWM v6 (I find a different version, boot into CWM v6, click install .zip from sd card and say CWM v5 launches, but when I reboot it's back to v6)

Flash stock rom via odin....
Flashing other diffrent ROM packages won't help until you have right bootable kernel...
So put your efforts towards making it to boot up on a stock firmware....
By ODIN mode
Try installing drivers and checking that no other device is connected to pc via USB.
Also make sure you follow the guide properly....
Then post errors ...or try google...
We'll help...
Sent from my GT-S5360 using XDA Free mobile app

Stuck when flashing X720

So I've finally mustered up some courage to flash something fancy into my X720, and this is what happened. Up until flashing the ROM itself ([ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722) by mosimchah) it went relatively well, but then I got twrp error 7. After some tweaking error message changed to "failed to mount '/system' (invalid argument). Can it be because I've wiped "system" before flashing? I think instructions said to do so... Anyway now I'm stuck, because even though I made a twrp backup, I was smart enough to remove it from the phone and now I can't put it back, because one of the files is 4gb in size, and I get error message when trying to copy it to phone storage (file system indicates "generic" or something along those lines). I'm new with this kind of stuff, so I really could use some advice. Should I flash stock rom? If so, which version? I can't remember exactly which was mine. I wonder if there's something to be done with that 4gb recovery file? And how did twrp mess up like that? Shouldn't it be calculated more carefully?

TheOkMan said:
So I've finally mustered up some courage to flash something fancy into my X720, and this is what happened. Up until flashing the ROM itself ([ROM] [TREBLE] [8.1] [Official] AICP 13.1 (Pro3 aka zl1, zl0, X727,X720,X722) by mosimchah) it went relatively well, but then I got twrp error 7. After some tweaking error message changed to "failed to mount '/system' (invalid argument). Can it be because I've wiped "system" before flashing? I think instructions said to do so... Anyway now I'm stuck, because even though I made a twrp backup, I was smart enough to remove it from the phone and now I can't put it back, because one of the files is 4gb in size, and I get error message when trying to copy it to phone storage (file system indicates "generic" or something along those lines). I'm new with this kind of stuff, so I really could use some advice. Should I flash stock rom? If so, which version? I can't remember exactly which was mine. I wonder if there's something to be done with that 4gb recovery file? And how did twrp mess up like that? Shouldn't it be calculated more carefully?
Click to expand...
Click to collapse
You can use a SD card or a USB otg and a flash drive for your backup
Sent from my PH-1 using Tapatalk

clsA said:
You can use a SD card or a USB otg and a flash drive for your backup
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip, clsA. Gave me quite a push. However, here what happened next: with USB OTG I was able to move the missing 4gb file to the phone storage and recovered my phone to a fully working state (wasn't able to recover directly from USB - anyone knows why? Maybe because it's ntfs?). Thinking I've established a good pivoting point I proceeded flashing custom ROMs. First time I did everything the same. The result was same, obviously. Then recovery. Then I tried leaving *system* out of wiping process and switched my ROM from AICP to DotOS. Installation went through without errors, but the ROM wasn't working correctly. SIM card wasn't recognized, HOME and DETAILS capacitive buttons wasn't working, couldn't download apps from play store, some crashing here and there. I though I had enough, and decided to recover for the time being, but when I did that upon boot up I got *ENCRYPTION UNSUCCESSFUL* error. There's restore system option under it, but it doesn't help. Tried recovering again - same. Reflashed DotOS - got my SIM recognized, but all other bugs remained. I think I'm doing something wrong when flashing, but can't figure out what. There isn't that many steps, and I followed them through... Even tried removing first lines of that script file (in ROM zip file) to get rid of that error 7 at the beginning of AICP installation, which didn't do anything (there's also a chance I've deleted wrong lines, or not all of them..). Maybe someone had similar problems and could share some ideas? And that Encryption error is very strange. Nothing changed after first recovery, so why I'm getting it? All the directories are in ex4 format. Any thoughts about this one?

TheOkMan said:
Thanks for the tip, clsA. Gave me quite a push. However, here what happened next: with USB OTG I was able to move the missing 4gb file to the phone storage and recovered my phone to a fully working state (wasn't able to recover directly from USB - anyone knows why? Maybe because it's ntfs?). Thinking I've established a good pivoting point I proceeded flashing custom ROMs. First time I did everything the same. The result was same, obviously. Then recovery. Then I tried leaving *system* out of wiping process and switched my ROM from AICP to DotOS. Installation went through without errors, but the ROM wasn't working correctly. SIM card wasn't recognized, HOME and DETAILS capacitive buttons wasn't working, couldn't download apps from play store, some crashing here and there. I though I had enough, and decided to recover for the time being, but when I did that upon boot up I got *ENCRYPTION UNSUCCESSFUL* error. There's restore system option under it, but it doesn't help. Tried recovering again - same. Reflashed DotOS - got my SIM recognized, but all other bugs remained. I think I'm doing something wrong when flashing, but can't figure out what. There isn't that many steps, and I followed them through... Even tried removing first lines of that script file (in ROM zip file) to get rid of that error 7 at the beginning of AICP installation, which didn't do anything (there's also a chance I've deleted wrong lines, or not all of them..). Maybe someone had similar problems and could share some ideas? And that Encryption error is very strange. Nothing changed after first recovery, so why I'm getting it? All the directories are in ex4 format. Any thoughts about this one?
Click to expand...
Click to collapse
follow instructions posted here > https://forum.xda-developers.com/showpost.php?p=77813881&postcount=793

clsA said:
follow instructions posted here > https://forum.xda-developers.com/showpost.php?p=77813881&postcount=793
Click to expand...
Click to collapse
Thanks again, clsA. Looks like this could be it. Will try it soon. For now I have flashed [ROM][X72X][7.1.X][OFFICIAL] LineageOS 14.1 (which is now 8.1 somehow...) and it works without any issues so far.
Any insights on why I'm getting *Encryption unsuccessful* error after restoring my original system image via TWRP (first recovery was fluent, error appeared following my later attempts for recovery)?