Related
Hi all,
Thanks to those who have helped along the way. None of this is my work, I am just putting it all in the one place for those who are in a similar situation as me - wanting to do get onto JG5, but not knowing how. Hopefully you can follow along!
This is the first time I've ever done anything to an Android phone, so consider me a noob! Here's all the files I used - multiupload.com/66CNCCTE4W (you will need to copy and paste the link into your address bar as I can't post links yet
Before you start, I did this on my Australian Samsung Galaxy S, so I'm not sure how different your model is!
Before starting, unzip the downloaded file above to your hard drive, and extract it to an easy to find folder - I'd suggest somewhere on your desktop.
1. Open the Odin3_v1.0 folder
2. Run Odin3_v1.0.exe program
3. Select the PIT, PDA, Phone and CSC files by clicking on the button, then locating the file in the I9000XWJG5 folder
a) PIT - s1_odin_20100512.pit
b) PDA - CODE_I9000XWJG5.tar
c) PHONE - MODEM_I9000XXJG1
d) CSC - CSC_I9000OXXJG4.tar
4. Remove the External MicroSD Card and the Sim Card
5. Turn the phone off
6. Get into download mode by pressing volume down + home key + power button
7. Connect the USB Cable from phone to computer
8. Wait for the drivers to be automatically installed.
9. Once drivers are fully installed, click START in Odin.
And that should be it!
P.s. I had to manually select my Network by going into Settings, Wireless and network, Mobile networks, and then selecting the Network (for me it was Optus). You will probably want to select Swype as the default input. To do this, press and hold a text input field, and press input and select Swype.
I hope this helps - please let me know how it goes for you!
*(Edited to include only flashing phone - I originally thought you had to root it first!)
You don't need to do step one and two.
lol,why bother about root ur device when u can straight away flash it like step 3??
Why do we need step one and two before ?
Since we are going to flash new rom and will need to do those again ????
Didnt work
So i tried to flash my SGS last night but it didnt turn out so well.
put all the bits and bobs in (.pit pda phone and modem) and then connected the phone in Download mode, seemed to connect to Odin, ID:COM 0:[COM20], clicked start, it seemed to be working so went to check on dinner and when i came back it didnt seem to be doing much, screen on the phone was blank and odin looked like it was tring to move across factoryfs.rfs, i look in the CODE file and saw that the factoryfs.rfs file was huge so thought id just leave it and wait. but nothing left it for 4-5 hrs then left the comp on all night when i cam back it was in the same spot but said removed and the phone was showing a phone then triangel with a ! inside the computer. so i unpluged it took out the bat and put it back tried turning it on, same thing, turned it off again and put into download mode seems to work but didnt get a chance to play with it at home, at work now and cant do it because it asks for admi privileges to install the drivers, so ill wait till im home again. anyone got ideas of what it might be? should i have connected to port 7?
Really? There ya go. Told you I was a noob! Sorry to confuse people. I have edited the original post so it only shows the flashing part.
#4 is not needed.
BTW: your tutorial is already stickied in the big faq (post 2).
I think alot of noobs will find this very useful. It's easier to follow for those who are flashing for the first time, i'm sure others wil appreciate your effort.
ZacJ said:
Really? There ya go. Told you I was a noob! Sorry to confuse people. I have edited the original post so it only shows the flashing part.
Click to expand...
Click to collapse
Hey Zac,
Don't worry if the steps are already in post # 2. I find yours better and more direct. More importantly, your phone is also from Australia, same as mine.
Thank you for taking the trouble to post this. I've been helped. I'm a bigger noob I guess
The only problem is that I don't seem to be able to download it. It stops after a few bytes. Know of any alternative links?
Edit: On the other hand, after going through some of the comments on threads related to JG5, all the problems are still there, so I don't see any real advantage over JG3. Will stick to this, since I'm about to get a replacement for my phone soon.
Thank you!! Thank you!! Thank you!! Thank you!! Thank you!!
I really want to thank you 4 this!! Damn you're the man!! This fixed my broked SGS immediately!! I can't thank you enough my best friend 4 ever!!
How do i get Superuser in to this?? And can i use Lagfix 2.0 too?? Please answer to me..i'm so so so damn gr8ful about all your hard work! Do i have to root my SGS again and where i can find the latest file update.zip which works with this your version?? I have already update.zip but it's kinda old file though.
Like i said earlier:
Thank you!!
Thank you!!
Thank you!!
Thank you!!
Thank you!!
PS: I gave 5 stars !!
Dude don't stress!
For rooting/superuser read my tutorial!
http://forum.xda-developers.com/showthread.php?t=728754
After that you can either apply One click lagfix or the CFLagFix 1.80!
I would recommend CFLagFix 1.80!
Buy me a beer if it works
LauncherPro problems
Hiya!!
U have any idea when i installed this jg5 my launcherpro won't work anymore at all, it just force closes all the time and i can't open my phone at all?? Why this is happening??
How do install this but still use LauncherPro??
( Though it works when i install it but immeadiately when i try ty restart my LauncherPro it starts to force close 24/7)
When i did a factory reset it didn't make it completely, it left something in in phone about this jg5...maybe that's why my LP is not working anymore...
Sorry but i'm a noob so don't judge me, i have a question now, where i can get "Stock 2.1 Eclair"?? I have now FRF91.372 2.2 in my phone it works like ****!! I don't even get LauncherPro work without continious force closes...i want that firmware where LP works without any force closes!!
Please help a noob...please, now i know how to use Odin, cause i have flashed already 3 times. But all the firmwares what i've tried have sucked.
PS: Is there any way i can do a raw clean for my SGS before install new firwmare, i ask cause i want to SGS completely empty before i install new firmware, is this possible?? I heard that if you swype your SGS empty new firmware will work much better...but this is just a rumour though
Gothic Touch said:
Sorry but i'm a noob so don't judge me, i have a question now, where i can get "Stock 2.1 Eclair"?? I have now FRF91.372 2.2 in my phone it works like ****!! I don't even get LauncherPro work without continious force closes...i want that firmware where LP works without any force closes!!
Please help a noob...please, now i know how to use Odin, cause i have flashed already 3 times. But all the firmwares what i've tried have sucked.
PS: Is there any way i can do a raw clean for my SGS before install new firwmare, i ask cause i want to SGS completely empty before i install new firmware, is this possible?? I heard that if you swype your SGS empty new firmware will work much better...but this is just a rumour though
Click to expand...
Click to collapse
All the ROMs that are released by Samsung themselves are stock ROMs, e.g. JG5 is a Stock Eclair 2.1 ROM.
hi guys,
I hope someone can help me.....
today I install some app to give extra animation and crap but after I ve done it the phone keeps restarting after I slide the srceen to unlock it.
I have done a hard reset formated the phone and cache and still the same,
I have also tried to flash it but RDS came back with " unable to retrieve info from INI file.
sim card is in but there is still "no service" on,
I ve looked through the forum but non of the posts seems to desrcibe my problem.
cheers,
p.s I forgot to add that my rom was 2.51 uk as far as I aware
regards,
hi,
the 'unable to retrieve ini file' could be because of your usb ports.
however,
if you go to recovery mode( hold vol- during startup then vol+ and vol- simultaneously when you see a little green man) you should be able to get a menu which will let you do a factory reset( clear data) which should make the phone work.
cheers
hi,
yes and I ve done it twice already and still rebboting after unlocking the screen
ane other ideas??
I ve treid to dowload rom but it wont extract and the other one saying that about ini file.
cheers,
hi again,
were you trying to install a flashlight fix zip btw before all this happened?
if so, the only option is a full flash.
try it with a different computer but i think at this moment rsdlite is the only hope.
i know because it has happened to me quite a lot.
cheers
hi,
I thinking the same, however, every rom I download doesnt work,
and now stupid question...where can I get a uk rom from??
cheers,
just check the android development section for the defy,
there are plenty of choices for a uk rom.
download one and flash it with rsdlite from a computer with usb 2.0 .
thats the cause of the ini error apparently.
good luck.
hi,
any link please??
I ve not been lazy its just I dowloaded two already and none of them work,
and now even RSD wont find the phone...just great saturday hahaha
cheers,
http://m.cfa.aero/
credit to fritolays.
go to the last link. CEE deblur< download that.
for rsdlite, keep trying, youll get there eventually.
thanks would be appreciated.
cheers
hi,
I will keep trying and if it wont help then I will have to go to t mobile and change my handset again,
Thanks a lot amansth
.....right guys please RSD saying couldnt retrieve values from INI file, I dont have access to any other PC so is thre any other way??
I ve got one txt file in the folder with firmware with this number in 09a6752e6119bb69c02d02f06a68d17e maybe that just need changing?? I dont want to mess about with it too much cos I m just a rookie
thanks,
...... Hi guys,
After a 6 hour fight I finally managed to flash my phone and it works, old RSD for some reason wouldnt support the phone so I got the new one and I could sleep much better
The only issue is that I liked 2.51, not necessarily the whole blur thing but I still think software looks much better and for example, mail box wont open, not the google one but the other that Ive added. Market place looks quite old compare to how it looked on 2.51, for eg the buttons for apps,games and apps look like big grey brick where in the other one there where nicely "implemented" into the market website.
however, I could not load 2.51 on my phone because it would stay on black screen with white LED on. I ve tried couple of times and always the same.
maybe I m doing something wrong?? what are those 2.51 boot only for?? I ve tried to put that in first then the firmware and still the same.
thanks all,
hi,
sadly, downgrade to 2.51 isnt possible because you upgraded to the froyo roms, the bootloader is newer so it is impossible to go back.
still, the froyo roms are generally better but somehow they seem laggy sometimes.
hopefully since motorola is pushing beta builds and the actual froyo release will come out around april- may you wont have to stay with the blocky icons for long.
Hi guys.
I just got a defy, first smartphone I have so I have no idea what I'm doing, I'm just trying to follow what seems to be the most popular guide to put CM7 on it.
Current question:
1) How do I check whether my phone is rooted properly?
2) In settings -> applications - > manage applications -> All > I can see SndInitDefy in the list (also under Dowloaded tab). If I click on it I can choose "uninstall". Could I do something wrong by uninstalling it and then installing it again?
Replies are greatly appreciated as I'm waiting for somebody to help me out so i can continue
Previous questions (solved):
When I want to put the recommended sbf file on it with RSD Lite 4.9 I can't. "Start" stays greyed out:
Anybody know what I'm doing wrong?
Click to expand...
Click to collapse
Check lastest Motorola drivers. If not work, change to another pc to test.
Thanks for the reply.
I installed all the drivers and managed to root it.
I'm wondering, should I do anything besides just plugging in the phone and trying to run the program, or should i somehow get it into "bootloader mode", I've read that somewhere but not sure...
Nietzschean said:
Thanks for the reply.
I installed all the drivers and managed to root it.
I'm wondering, should I do anything besides just plugging in the phone and trying to run the program, or should i somehow get it into "bootloader mode", I've read that somewhere but not sure...
Click to expand...
Click to collapse
Yes you need the phone in bootloader.
To do that turn the phone off & then press & hold the volume UP button then press the power ON button. The phone will then go into bootloader & you can then connect the USB cable to the PC ready for RDS Lite flashing
Follow this great guide by Higgsy regarding the RDS flashing process - http://forum.xda-developers.com/showthread.php?t=853674
Alright, I got it into bootloader mode and the phone itself says
Battery ok
ok to program
transfer mode:
usb
But still no joy
Also, I wonder whether it's ok to use that sbf file:
JRDNEM_U3_3.4.3-11_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P010_A007_HWp3_Service1FF
It says USA but I'm in Europe, does it matter? I got it from the guide mentioned in my first post, apparantly it's "the one that Quarx used"?
sp8y said:
Follow this great guide by Higgsy regarding the RDS flashing process - http://forum.xda-developers.com/showthread.php?t=853674
Click to expand...
Click to collapse
Took a look at it, he says "##WARNING: be careful when flashing 2.51 firmware, firstly its patched so root isn't achievable by the usual methods, and isn't easy to downgrade back to other firmware - I suggest you search and read the various topics on it. My advice is to use 2.21 UK or 2.34 Deblur firmware##"
I just got the phone so i'm guessing it's 2.51 firmware. Is it necessary to upgrade it first?
Also, how do I know which country my phone is from?
If I shouldn't use the version which Quarx used on a European phone, I have no idea which one to pick from these:
http://and-developers.com/sbf:defy
Some more more info about the phone:
system version: Blur_Version.2.21.0.MB525.Retail.en.GB
firmware version: 2.1-update1
Nietzschean said:
Took a look at it, he says "##WARNING: be careful when flashing 2.51 firmware, firstly its patched so root isn't achievable by the usual methods, and isn't easy to downgrade back to other firmware - I suggest you search and read the various topics on it. My advice is to use 2.21 UK or 2.34 Deblur firmware##"
I just got the phone so i'm guessing it's 2.51 firmware. Is it necessary to upgrade it first?
Also, how do I know which country my phone is from?
If I shouldn't use the version which Quarx used on a European phone, I have no idea which one to pick from these:
http://and-developers.com/sbf:defy
Some more more info about the phone:
system version: Blur_Version.2.21.0.MB525.Retail.en.GB
firmware version: 2.1-update1
Click to expand...
Click to collapse
OK your phone looks like it's a UK version running Blur version 2.21 & Android 2.1 eclair.
The sbf you are trying to flash - 3.4.3-11 is a UK froyo with MotoBlur (the USA bit in the filename is nothing to worry about & is OK to use) - it is a good ROM & I used to have that myself until I flashed the Nordic deblur sbf.
The warning that Higgsy mentioned was at that time version 2.51 had been released & it wasn't possible to downgrade to the older eclair versions.
I've only done a quick search in the Defy forums for the greyed out RDS Lite Start Button issue & there's some posts about it. But you could try uninstalling the RDS Lite & Moto Drivers programs then reboot your PC. Then reinstall, reboot your PC & try again with RDS Lite.
Hope this helps.
sp8y said:
OK your phone looks like it's a UK version running Blur version 2.21 & Android 2.1 eclair.
The sbf you are trying to flash - 3.4.3-11 is a UK froyo with MotoBlur (the USA bit in the filename is nothing to worry about & is OK to use) - it is a good ROM & I used to have that myself until I flashed the Nordic deblur sbf.
The warning that Higgsy mentioned was at that time version 2.51 had been released & it wasn't possible to downgrade to the older eclair versions.
I've only done a quick search in the Defy forums for the greyed out RDS Lite Start Button issue & there's some posts about it. But you could try uninstalling the RDS Lite & Moto Drivers programs then reboot your PC. Then reinstall, reboot your PC & try again with RDS Lite.
Hope this helps.
Click to expand...
Click to collapse
Alright, I'll try that and hope that works. Sucks to be so bad at stuff like this
Thanks man, appreciate it.
No problem hope it works out.
Have a search on the Defy forum if it doesn't work as I'm sure there's been a few others with that same problem you have.
If you can't get it to work post back on this thread & someone else may be able to suggest something that can help further
Here's a thread from someone with the same issue:
http://forum.xda-developers.com/showthread.php?t=1001145&highlight=rds+start+button
Have you got the RDS Lite program to run as "Administrator".
sp8y said:
Here's a thread from someone with the same issue:
http://forum.xda-developers.com/showthread.php?t=1001145&highlight=rds+start+button
Have you got the RDS Lite program to run as "Administrator".
Click to expand...
Click to collapse
I went to that thread and managed to do it, apparantly the problem was that the file was not in the C:\ directory but on my desktop.
In the end I got this:
So that seems to be ok, thanks for that. Now the following steps and hoping I don't brick it or I'll be dead in the water
I'm now going to try and get SndInitDefy_1.4_2.apk installed via the SD card...
Great nice one
Let us know how you get on with flashing the CM7 - I'm still yet to install it on mine - just waiting for a newer version then I'll give it a go
sp8y said:
Great nice one
Let us know how you get on with flashing the CM7 - I'm still yet to install it on mine - just waiting for a newer version then I'll give it a go
Click to expand...
Click to collapse
I wonder: if the new version comes out, will I have to do all these steps again or how does that work?
New problem:
I installed 2nd initi 1.42 from this thread:
http://forum.xda-developers.com/showthread.php?t=1032212
I rebooted the phone, pressing volume down while it was starting, and now I get a screen with a "triangle and an exclamation mark" and the little android guy
Phone doesn't do anything, can't even turn it off by pushing the power button...
edit: figured I'd just pull out the battery and put it in again, managed to turn it on normally again but I wonder what the problem was with trying to put it into the boot menu...
New problem:
The guide says:
"9. boot into boot menu by pressing the vol down button when the blue LED lights up on boot up"
But I never get a blue led like this guy does:
http://www.youtube.com/watch?v=h3ZHocqB2yI
I have no idea why I'm not getting a blue led
Does it mean 2nd init didn't install properly or something? (it said that it did)
from memory, it needs to boot up twice I think, for it to start working
Jakethepeg said:
from memory, it needs to boot up twice I think, for it to start working
Click to expand...
Click to collapse
I've rebooted 10+ times hoping to catch the led, no luck.
I would appreciate it a lot if somebody could tell me:
1) How do I check whether my phone is rooted properly?
2) In settings -> applications - > manage applications -> All > I can see SndInitDefy in the list (also under Dowloaded tab). If I click on it I can choose "uninstall". Could I do something wrong by uninstalling it and then installing it again?
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
doesitwork? said:
I attempted a root on Samsung Note 2 Sprint version (in white). Followed all steps, however phone got stuck in a reboot loop right after I put the option 2 (root only) Odin step in. Sprint ver LPH889 (I believe that is what Odin is calling it, option 72). Toolkit used was ADB 4.1.0.
Original symptoms were that the Android updater was looping trying to load everything; being new I made it worse and tried recoveries and reloads which also failed. Now it boots, goes to splash, circling blue oval image and...it stays there.
Good news: I have access to download mode and recovery reset mode (including sideloading).
Bad news: every thread I've followed has given me an issue.
I have recovery access but I need some idea of where to go from here and searches have shown near but not exact symptoms. I have unplugged it from the pc, removed the battery, done a factory reset, attempted to reflash via Odin (root) attempted to reflash stock via Odin and so far I am still stuck in a reboot loop. Windows detects the phone but shows a problem in device manager because possibly it won't stop rebooting. Any help you can provide is appreciated and if at all possible I need to recover some form of working phone here, and soon. My girl needs it for work and Sprint's network in my area barely works from day to day (which they admit but don't credit my account for). This phone has problems sending/receiving calls, they claim it's fine, and I was forced to try a root to get some form of working device. That failed too.
I'm a newb at this...it's been years since I flashed a phone (Razor v3), so...any help would be appreciated, otherwise I have to crawl to sprint/samsung and get it replaced, which I don't want to do. Thanks.
Click to expand...
Click to collapse
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
vel7wil said:
What method are you using to root.....I used the "toolkit" and had no problems at all.
http://forum.xda-developers.com/showthread.php?t=1957155....try this if you haven't already
Click to expand...
Click to collapse
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
doesitwork? said:
I thought it would to but I did not want to dig through 70+ pages of the thread when searching failed...unless I really needed to. Most of it is old and doesn't apply.
I was directed by the referenced Youtube vid. I used the options referenced for the phone in this thread with that toolkit. I backed up existing files (not as one unit, but internal files and I think OS), went for the option 2, followed the instructions and things went great through odin...until android went to update and started looping with the 'updating files' percentages. At that point I tried to restore to basic and started clearing caches and such and that is how I got to where I am.
When that failed I started looking at the leaked stock flash and that failed on shoot.ini which that guy never addressed because he thought his international version was all versions (that's why I choose 'doesitwork?' as screen name ). So i'm down to sideloading or something. I really need guidance, and I emailed the toolkit author but I'm still waiting on a reply.
Any thoughts?
Click to expand...
Click to collapse
When used the toolkit a year ago, I found that I had to turned off all firewalls and antivirus apps for it to work properly. Once I did that it worked fine....give it a shot...can't hurt......might even be able to repair what you've done so far.....Good Luck!!!
I'll give this my best shot...download a rooted rom from the development section and place it on your SD card.
Download toolkit from here (I take no credit for this) http://d-h.st/iu0
Put phone in download mode.
Open ODIN and uncheck "auto reboot". Then click "PDA" and add the .tar file (recovery).
Plug phone into PC (make sure to have samsung drivers installed).
Once ODIN sees the phone you can click "start".
When the recovery flash is complete, pull your battery to ensure power down.
Boot into recovery : volume up, home, power all at the same time.
Flash rooted rom.
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
---------- Post added at 08:14 AM ---------- Previous post was at 07:36 AM ----------
[/COLOR]
doesitwork? said:
Sorry for the late reply, I had some issues with the "catchpa".
The one click fix worked like a charm, thank you! I will soon be making a contrib to the site. It's a shame I couldn't root as easily :laugh: .
I know the level of work that goes into this stuff and the desire to keep on top of new gear while maintaining support for the old and I appreciate the community coming to my aid, so again, thank you!
Click to expand...
Click to collapse
It is usually a pretty common courtesy to hit the "thanks button" when someone helps you out.
I am not at all trying to be mean, just letting you know.
garwynn said:
Toolkit is an extra and unnecessary step.
http://rwilco12.com/downloads.php?d...ung Galaxy Note II (SPH-L900)/Stock ROMs/MC2/
Grab the one click flavor of choice. Use the one with 1090526 in the name as that's the full version.
Open in windows, put phone in download mode and flash. Easy Peasy.
Let me know if you have any issues with this.
Click to expand...
Click to collapse
hello @garwynn im trying to do this same thing.. its been so long since ive odin'd, how would i put TWRP on this now after these steps? i tried goomanager and that didnt work. (couldnt find recovery) and i tried flashing in stock recovery and got a fail . im kind of lost right now and am wondering if there is another way or do i have to do the toolkit? thanks
edit: for some reason, the tool kit links have been pulled by a mod. ..but this video helped me get twrp back. phew. zedomax to the rescue.. http://www.youtube.com/watch?v=7leb9OznhqY
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?
Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method
well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.
Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.
Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..
Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.
links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy