Related
Hello Im new to the forums
So I was trying to root my evo but i ended up messing it up. It wouldn't read the usb cable or charge and would also not read my SD card. I ended up being able to make it read my SD card but i still haven't been able to resolve the USB issue. I have searched several threads but all those methods of fixing the usb issue require your EVO to be rooted which mine is not.
does anyone know of a way to fix it without being rooted?
and i can't root my phone because it won't read the USB cable while the phone is booted up into android only in fastboot
bump.............
lancerevox279 said:
Hello Im new to the forums
So I was trying to root my evo but i ended up messing it up. It wouldn't read the usb cable or charge and would also not read my SD card. I ended up being able to make it read my SD card but i still haven't been able to resolve the USB issue. I have searched several threads but all those methods of fixing the usb issue require your EVO to be rooted which mine is not.
does anyone know of a way to fix it without being rooted?
and i can't root my phone because it won't read the USB cable while the phone is booted up into android only in fastboot
Click to expand...
Click to collapse
Trying to follow your problem so I'm assuming that your cable is defective. The OEM (HTC) cable provided with my Evo was defective and I had to torque the cable back at the neck of the connector to get it to work but sometimes it would still disconnect. I just bought another cable from eBay and problem solved, I had it in two days and it was cheap.
well i don't think the cable is defective because i can still connect it to the computer in fastboot and run adb commands thru the fastboot
is there a way to run the usb fix through fastboot usb from adb in the command prompt? i read the thread in which it shows the commands needed to fix the usb not reading but it requires super user and i was wondering if you can run that through fastboot instead
the cable isnt defective, you bricked your phone by rooting it incorrectly.
It's actually really hard to brick a phone. Your phone does not energize when it's bricked, hence the name.
You actually don't need a computer to root your phone so the whole USB cable doesn't have to be an issue. I read a post a while back by XDA users that rooted their phones without a computer and then found this on YouTube. I have NOT tried this but it appears plausible.
HTC EVO 4G from Sprint - How to Root and Unlock Nand Protection - Full Root No PC or ADB.
You have to understand that it's really difficult to give you solutions without knowing most of the parameters of your technical challenge. I don't think your phone is bricked but a defective phone is possible hence its irregular behavior--and I mean defective before you purchased it. But persist with this and you'll find that you'll learn a lot in the process. Good luck.
semperlux said:
It's actually really hard to brick a phone. Your phone does not energize when it's bricked, hence the name.
You actually don't need a computer to root your phone so the whole USB cable doesn't have to be an issue. I read a post a while back by XDA users that rooted their phones without a computer and then found this on YouTube. I have NOT tried this but it appears plausible.
HTC EVO 4G from Sprint - How to Root and Unlock Nand Protection - Full Root No PC or ADB.
You have to understand that it's really difficult to give you solutions without knowing most of the parameters of your technical challenge. I don't think your phone is bricked but a defective phone is possible hence its irregular behavior--and I mean defective before you purchased it. But persist with this and you'll find that you'll learn a lot in the process. Good luck.
Click to expand...
Click to collapse
thanks ill make sure to try this yeah i figured i did screw up the phone myself i doubt the phone was defective because it has worked flawlessly until i tried to root it and it messed up
ok well when i tried to flash the PC36IMG.zip it said update failed! main version is older. then it only gave me the option to reboot or not reboot?
lancerevox279 said:
ok well when i tried to flash the PC36IMG.zip it said update failed! main version is older. then it only gave me the option to reboot or not reboot?
Click to expand...
Click to collapse
I wish I could help you more but I've never encountered this problem. Try this thread? This user seems to be having a similar issue.. (going to read thread myself).
[EDIT 3] Worked fine, finally, thanks for all the help.
[EDIT 2] Yeah, I don't know how it happened or what happened, but I got a lot further. I started to get Odin failing at recovery and then remembered this thread which I found earlier: http://forum.xda-developers.com/showthread.php?t=907261&page=2
Basically did it exactly like how the OP fixed it, and the phone is currently being flashed.
But now I have a different problem, seems I can't get a break.
http://img651.imageshack.us/i/stuck.jpg/
It's stuck there, should I just wait? Is it supposed to take a while? Or is there a problem? Been there for about an hour now.
[EDIT] So the phone works now, but Odin won't flash for me. What could the problem be if it's stuck on Initializing (or rather, Initialzing as the program puts it)? I've tried 1.61, 1.7, used the DI18 file and removed the md5 bit so that the file ends in .tar, etc
Hey, so I've been desperately trying to return my Epic to stock DI18, and I tried clockwork mod which didn't work, and then I tried doing it through Odin, and it kept hanging on Initializing.
Anyway, I keep trying with Odin, and ended up taking out my battery and putting it back in, but now the phone won't turn on. It doesn't turn on normally, not through download mode, not recovery, nothing.
Any help? What can I do? I tried searching but every result ends up being about turning on bluetooth or wifi, etc., and the few that are related to bricking talk about going into download mode to flash with Odin.
I hope you didn't take the battery out while flashing odin...
you can't turn it on in any way right?
can you charge it via usb? maybe you just ran out of power while flashing?
Uh, yeah, that's exactly what I did. Every time Odin would hang at Initializing, I'd have to remove the battery and restart the phone to try again.
God, I am so stupid, it is ridiculous.
The battery did have a decent amount of charge last time I checked though.
Hold down 1 and power and insert battery while holding them. That should get you into d/l mode. Taking out the battery while odin is stuck on initializing does not harm the phone.
Sent from my Bonzai'd Epic 4g.
I just did something like what you said leather, and I got it into download mode.
Now I'm afraid to do anything. Any reason why my flashing through Odin wouldn't work?
Odin is picky about the computer its running on. I used a laptop when i first started flashing..no issues ever.
Fixed my desktop and instantly ran into odin problems. Try changing USB ports and make sure youve got no firewalls running.
Sent from my SPH-D700 using XDA App
Yeah, what I don't know how it happened or what happened, but I got a lot further. I started to get Odin failing at recovery and then remembered this thread which I found earlier: http://forum.xda-developers.com/showthread.php?t=907261&page=2
Basically did it exactly like how the OP fixed it, and the phone is currently being flashed.
But now I have a different problem, seems I can't get a break.
http://img651.imageshack.us/i/stuck.jpg/
It's stuck there, should I just wait? Is it supposed to take a while? Or is there a problem? Been there for maybe 5-6 minutes now.
The factory always takes the longest; so give it time. And do NOT pull the battery at that point. Youll have to say good bye epic :<
Sent from my SPH-D700 using XDA App
How did this end up? Did it move past FACTORY FS?
Nope, still stuck in that same exact place. Is it supposed to take this long or has something gone wrong?
Could I unplug it and try again at this point, or would that brick it? It's just stuck there, what do I do? I'd love to try different usb ports and such, but I can't if I don't stop this process, just don't know how to do it without bricking it.
And thanks for the help so far.
Did you remove the. Md5 at the end of the tar file?
Sent from my SPH-D700 using XDA App
No, I put the md5 back to start from the beginning with everything as it comes from downloads and such.
What do I do about it right now though? Can I safely unplug it and restart it or...?
Seems like you have no choice but to unplug it. Removing the md5 shouldn't make a difference. Try a different USB port.
Sent from my SPH-D700 using XDA App
Yeah, thankfully it didn't brick. I feel like I'm walking through a minefield with this thing.
Anyway, switched ports, had the file renamed to end in .tar, made sure Odin was opened as administrator in Windows 7, and thankfully it flashed fine.
Now I'm back at vanilla 2.1, can start fresh in terms of upgrading, was having some problems earlier. Is that GPS locking problem present in 2.3? Assuming I put ClockworkMod 3 on it and have the file system reset to EXT4, can I just flash to 2.3 ROMs right away?
Such problems
Hi everyone,
Skip this first paragraph if you just want to read my steps from problems to solution:
I hope this post helps people who were in the same situation I was in.
A few days ago I just happened to read the news about the new gingerbread for the AT&T i997 Samsung Infuse. I read that it wasn't over the air. Because of what has been seeming as a bluetooth leak after trying everything to stop the leak up to hard resetting it, I figured I'd pray that gingerbread fixes it. So on went my quest in the last few days trying to get this gingerbread update as fast as I could.
1) I downloaded keys mini for the Samsung device which was needed for the upgrade. I installed it on my main pc which is windows 7 64 bit. After installation, it's first run, it automatically updated the application.
2) I plugged in my phone via usb and it said device not registered so I got in contact with a Samsung rep in chat who told me to register it and it would take 24 hours.
3) I registered on Samsung and waited about 48 hours and still no change.
4) Got impatient and read about GTG Ultimate unbrick which is supposed to return my stock phone back to it's out of box condition which eliminated what I thought as an error with my phone of it not being registered.
5) Now after plugging it in after the unbrick. I got a message stating "device already up to date". I kept getting this for the last couple days. Sigh
6) Read that I could download the new gingerbread stock ROM without being rooted. Just had to use the ODIN3 I got with the GTG Ultimate unbrick zip file and supply the ROM I997UCKL2-Homebinary.tar.md5 as the input file.
7) Follow basically same instructions as unbricking but not reformatting and just supplying the md5 file as the input for hte PDA button then clicking start.
8) Odin 3 message status window was stuck at setupconnection and I knew this wasnt right. It was stuck for over 15 minutes and it should only do that for a minute or less.
9) Unplugged usb and big error in red on Odin 3 (but didn't have a choice)
10) Tried removing battery and retrying the flash but now a bigger issue the screen was all colored specs or in other words multi colored spots. Rut roh!
11) After scratching my head and googling like crazy some others had the same issue and they mentioned removing the battery and trying again but didn't mention that the spots would remain on the screen while the items could be flashed fine.
12) Tried again this time it got past setupconnection but was stuck at initializing.
13) Thought to myself let me try it on my Windows Vista 32 laptop.
14) Voila. It worked. So don't give up if you see the colored spots on your screen. There still is a chance. I now have gingerbread. THANKS EVERYONE!
Next Morning Update:
I was too quick to be happy. It seems I am one of the small few who is having touch sensitivity issues and lag typing on the lower right side of the screen especially with the back key (backspace). I typed my first reply to an email and the third word in the backspace was completely disabled.
Glad you got it working.
Am i the only one when i saw "what now" immediately thought about that lead paint commercial ?
iSaint said:
Am i the only one when i saw "what now" immediately thought about that lead paint commercial ?
Click to expand...
Click to collapse
GTG Ultimate unbrick zip is missing can u re-up it plz?
Hi,
I hope someone could help me about my A3000 device. I have done flashing my tablet for the first time and it worked fine after that (following the steps from here: http://forum.xda-developers.com/lenovo-a3000/development/rom-lenovo-ideatab-a3000-h-call-t2441135). Unfortunately, after a few weeks, I have installed a lot of apps and it crashed or simply not working anymore.
I tried to do flashing again for the second time but unluckily, it doesn't take effect anymore. It always gets stuck at 44% of flashing, (ticked all the files displaying in the SP flash tool through the scatter file). Now, I tried flashing the files one by one. I found out that the ANDROID file has the problem. It won't completely download. All the other files like Recovery, Bootimg, UBOOT, EBR1 etc. works fine and it confirms with the "DOWNLOAD OK."
I have tried different options with Firmware Upgrade, Format all + Download etc. I also did perform Format in the SP Flash Tool before Downloading.
I hope you guys can suggest what step I should do next.
Thanks!
-Jules:fingers-crossed:
fix
Hello,
I had the same problem on my jiayu s3. but when i used another usb cable and another usb port it works. It sounds like bull**** but just try another cable.
good luck!!!
Same problem on A3000, I tried all the roms I have with all the sp tools' versions I have on windows and linux! (I never get the flashing to start beyond the red line on linux by the way) with no luck at all.
and no, formatting is not an option, I don't have nvram backup...
seems that our dear old tabby has expired or something, there are like 5 threads speaking about the same problem which I had..
however, I know that you can't charge the battery unless the system is up, so flashing is using the already leftover battery charge, it seems that our batteries turn old so that leftover part is getting really low that flashing never get complete in big files like android.img.
So our pal @RayA3000 is trying replaceing the battery in hope that this will work. let's wait and see, I'm too timid to invest in a new battery that will cost me whopping 150 EGP...
it is because your IC. Change your IC with a new One
can u pls help me to make my lenovo a369i device work properly
Hello Guys,
yesterday I restarted my Nexus 4, running the cm-13.0-20160520-NIGHTLY-mako. It stuck at the bootlogo, so I tried to reflash it in the twrp 2.8.7.0 recovery. But I got the error message "E:/ unable to mount /cache".
After that I was trying to solve this issue by wiping the cache, but I got the same error message -> The phone wasn't booting
From now on I did several things to solve my problem. I don't know the exact order.
- I've downloaded the Nexus Root Toolkit from WugFresh -> Tried to use the Flash Stock + Unroot Option with Soft-Bricked/Bootloop status enabled -> I choosed the 5.1.1 Factory Image -> In the cmd window, I get in every point the same error message "Falied (remote: flash write failure) -> I get the same message when I'm trying to manually flash each part of the factory image via fastboot
- Within the Toolkit I also tried to format cache, system and Userdata, but afther this I get the same error when trying to do the step before
- I think also used the Fastboot Flash options, but I'm not sure.
- After that I attempted to flash the cm13.zip via adb-sideload in TWRP. Here is a part from the error message I get:
"(...) could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume (...)
E: Error executing updater binary in zip 'sideload/package.zip'
E: Unable to mount '/data'
- In TWRP the Internal Storage is shown with 0mb
- Currently only the bootloader is working fine and I also can get a fastboot and adb connection to the phone
-> Loading the recovery is only possible by booting a recovery image in fastboot
Can somebody tell me if it is possible to restore my Nexus 4 and how to do it?
Thank you in advance :fingers-crossed:
PS: I hope I mentioned all the important points. If some information is missing, feel free to ask me.
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
audit13 said:
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Thank you for your answer.
I tried to flash the newest cm13 in TWRP and with adb Sideload. I get the same error.
Also the 4.2 Stock rom doesn't work. Same problem as with the 5.1.1 factory image.
I also switched the cable and the USB ports, but it leads to the same error messages.
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
audit13 said:
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
Click to expand...
Click to collapse
I get the same error message as always: Falied (remote: flash write failure)
nerotNS said:
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
Click to expand...
Click to collapse
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
audit13 said:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
Click to expand...
Click to collapse
Unfortunately yes. After locking the bootloader via fastboot, the bootloader is marked as unlocked after rebooting.
Do I have to change the mainboard?
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
audit13 said:
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
Click to expand...
Click to collapse
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
tobi.king said:
I get the same error message as always: Falied (remote: flash write failure)
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Click to expand...
Click to collapse
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
tobi.king said:
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
Click to expand...
Click to collapse
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
nerotNS said:
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
Click to expand...
Click to collapse
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
tobi.king said:
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
Click to expand...
Click to collapse
Awesome, glad to be of service
So, I figured my mistakes can save some others some grief. Part of the problem is that this phone is relatively new and information is scattered all over so it is hard to find all that is necessary at a singe source.
I had the Amazon Prime 8 gb with 6.1 firmware. I first installed the SP Flashing tool and flashed the TWRP_Scatter_R1_Prime.zip. I already had the MTK preloader drivers installed. I then flashed the TWRP scatter file, Download Only, and all went well. I did a complete back up to my SD card. I wanted to run the debloating scripts at this point, but I had missed installing them on the SD card, so I installed SuperSU from TWRP after pressing Vol+ and power to reboot. Then I did a regular reboot. The phone booted just fine so I added the scripts to the SD card. I then rebooted into TWRP and ran all three debloating scripts and rebooted. Again, all went well.
Here is where I made my First Error. I reset the phone to factory defaults so I could go through the setup procedure. One of the video guides suggested this. I am assuming that one of the debloat scripts deleted the setup procedure since I now wound up in a perpetual loop where the phone kept telling me it could not run set up.
So, as I had made a complete backup in TWRP, I rebooted into TWRP and did a restore from my back up file. FAIL. No idea why. I then went to the video outlining the procedure for restoring a bricked phone using SP Flash and the correct txt file for flashing the default 6.4 firmware, being told that updating was OK. ERROR. SP Flash said I needed to re-run using the setting Format+Download.
Second Mistake. Half way through, another ERROR. And I now had a total brick. No recognition on a PC; no TWRP boot; no power up no matter how long I held the power button. DOA.
Please weigh in on anything I am missing or am mistaken on. Also, help other users in pointing out anything I did wrong and missed. At least this is only $50. But I am skipping this phone and staying with my old model.
chas0039 said:
So, I figured my mistakes can save some others some grief. Part of the problem is that this phone is relatively new and information is scattered all over so it is hard to find all that is necessary at a singe source.
I had the Amazon Prime 8 gb with 6.1 firmware. I first installed the SP Flashing tool and flashed the TWRP_Scatter_R1_Prime.zip. I already had the MTK preloader drivers installed. I then flashed the TWRP scatter file, Download Only, and all went well. I did a complete back up to my SD card. I wanted to run the debloating scripts at this point, but I had missed installing them on the SD card, so I installed SuperSU from TWRP after pressing Vol+ and power to reboot. Then I did a regular reboot. The phone booted just fine so I added the scripts to the SD card. I then rebooted into TWRP and ran all three debloating scripts and rebooted. Again, all went well.
Here is where I made my First Error. I reset the phone to factory defaults so I could go through the setup procedure. One of the video guides suggested this. I am assuming that one of the debloat scripts deleted the setup procedure since I now wound up in a perpetual loop where the phone kept telling me it could not run set up.
So, as I had made a complete backup in TWRP, I rebooted into TWRP and did a restore from my back up file. FAIL. No idea why. I then went to the video outlining the procedure for restoring a bricked phone using SP Flash and the correct txt file for flashing the default 6.4 firmware, being told that updating was OK. ERROR. SP Flash said I needed to re-run using the setting Format+Download.
Second Mistake. Half way through, another ERROR. And I now had a total brick. No recognition on a PC; no TWRP boot; no power up no matter how long I held the power button. DOA.
Please weigh in on anything I am missing or am mistaken on. Also, help other users in pointing out anything I did wrong and missed. At least this is only $50. But I am skipping this phone and staying with my old model.
Click to expand...
Click to collapse
With format+download make sure preloader is not checked....
For anyone interested, BLU really doesn't want to repair the phone. Their regular rep said that I needed to send it back to Amazon as it was too early for them to repair it even with the warranty voided. I got a supervisor and they said that actually, they would fix it and the current cost with no physical damage would be $28.50. So with $4 shipping on my part I am back in business.
So anyone with a 6.6 brick has an option that is not too bad.
chas0039 said:
For anyone interested, BLU really doesn't want to repair the phone. Their regular rep said that I needed to send it back to Amazon as it was too early for them to repair it even with the warranty voided. I got a supervisor and they said that actually, they would fix it and the current cost with no physical damage would be $28.50. So with $4 shipping on my part I am back in business.
So anyone with a 6.6 brick has an option that is not too bad.
Click to expand...
Click to collapse
If you had a Prime version and it was within the first 30 days of purchase, you could've send it back to Amazon to get a replacement, no questions asked, for free (this only works once by the way). Either way, glad to see Blu is willing to fix our mistakes. Maybe request that your R1 is restored with older, non-6.6 firmware. Probably won't work, but it's worth a try.
But do note that if you send it back to Blu for repair, it is very likely that when you get it back it will have the latest 6.6 update on it that disables SPFT so you won't have root, be able to disable ads, flash non-prime rom or any of that stuff.
yaconsult said:
But do note that if you send it back to Blu for repair, it is very likely that when you get it back it will have the latest 6.6 update on it that disables SPFT so you won't have root, be able to disable ads, flash non-prime rom or any of that stuff.
Click to expand...
Click to collapse
My guess is, they will load it with the factory shipped image, unless QA loads the update during testing, but perhaps they wont.... Kinda like a roll of the dice on this one...
I found a similar problem on an other mtk device thread. Where either through formating or failed flashing that you end up in am appearently dead device. If it is the same, it is from the battery stats getting woped out. And the solution is to leave it plugged in for two to three days then try to connect to spft again.
I am skepticle but what harm could if do to try.
I beleive the boot ROM section is not writeable and not formatable. (The first 2mb of device chip) so, it should be seen by PC as some kind of com port
I did not have success flashing pree loader with spft but @Persuasion89 has recovered his phone and as soon as he replies to my request for a file list you should be all set for a repair.
This is why I just paid the extra $50 and bought the ad free version. $110 is still a great price for the device, and no hassles with any ad removing nonsense
mrmazak said:
I found a similar problem on an other mtk device thread. Where either through formating or failed flashing that you end up in am appearently dead device. If it is the same, it is from the battery stats getting woped out. And the solution is to leave it plugged in for two to three days then try to connect to spft again.
I am skepticle but what harm could if do to try.
I beleive the boot ROM section is not writeable and not formatable. (The first 2mb of device chip) so, it should be seen by PC as some kind of com port
I did not have success flashing pree loader with spft but @Persuasion89 has recovered his phone and as soon as he replies to my request for a file list you should be all set for a repair.
Click to expand...
Click to collapse
Im sorry for the delay, ive been trying to drop a transmission into my car but I'll try to get a list together for you tonight. I did some manual tinkering with my scatters and frankenstein work with file lists so i'll need some time, but ill get back to you when i can.
I wish I have seen this before bricking mine......
How did you brick it? I have rooted and twrped two of them now without any issues. What did you do that people need to be careful to NOT do?