Related
I tried to root my 3G XOOM (MZ606) last night and eventually I did brick it but I am not sure. I did definitely dl the wrong img file (as I didnt read here before Anyway everything of the procedure went fine till I had to type the commands (like adb remount) after reboot. Actually the XOOM does not seem to connect to my wireless hotspot anymore (is that due to a missing key?) and it remains in the boot up screen (just the MOTO logo)
Is there any solution to get the XOOM reconnected may be? Can anyone push me into the right direction? Do I really need those certain cable (someon mentione in any thread here)?
--
thanx a lot for your help
Michael
if you have ANY type of screen coming up, its not bricked. Depending on your situation, you just need someone whos good with ADB/Fastboot to get things back to where they need to be.
---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------
go into recovery and wipe Everything/ factory reset, wipe cache, and go into advanced and wipe dalvik cache. then flash any rom available here in the DEV section.
hmmm I found out how to do that
>go into recovery and wipe Everything/ factory reset, wipe cache
but what means
>and go into advanced
? There is no advanced option at the recovery menu. So may be thats an otion once I choose 'reboot system now'?
And just for my understanding, that
>then flash any rom available here in the DEV section
is not necessary just may be in my interest, right?
--
Thanx anyway, great help
Michael
It might help us if you tell us what model your Xoom is...3g/wifi - us/uk - all the specifics.
Hopefully you knew this before you installed the wrong image.
Then we can help you get back to where you need to be.
And 'flashing any ROM here in the development section' is what got you here in the first place so I wouldnt do that.
Hola,
well I will definitely be more careful now. Actually I did read about those issue with the Wifi only device before but... So what specifications I could deliver?
So far I saw on the screen also printed on its backside its an MZ606 purchased from MOTOROLA china directly. I possibly wouldnt have tried to lunlock and root if those gadget could at least connect to the google market... sorry for complaining but the cn.MOTOROLA market does have very few and mainly chinese apps only. Further on before the procedure I stuck in now the OS has been Android 3.1
Hope those background information allows some more conclusions but
right now I am still trying to figure what kenfly ment by mentioning
>go into advanced and wipe dalvik cache
If I understand for example those guys http://forum.xda-developers.com/showthread.php?t=560207 right (hopefully it is allowed to put that link here) it seems to be a procedure before flashing a new ROM. What I am asking myself is do I right now not have a working one anymore? May be I misunderstood in the past but so far I thought the sequence is unlock> root> custom rom... and so far I think I am not successfully rooted yet so I wouldnt be supposed to flash a new ROM. So I think what I need to do now is to get my device successfully rooted before wiping the 'dalvik cache', am I wrong?
--
Cheers Michael
[email protected] said:
Hola,
well I will definitely be more careful now. Actually I did read about those issue with the Wifi only device before but... So what specifications I could deliver?
So far I saw on the screen also printed on its backside its an MZ606 purchased from MOTOROLA china directly. I possibly wouldnt have tried to lunlock and root if those gadget could at least connect to the google market... sorry for complaining but the cn.MOTOROLA market does have very few and mainly chinese apps only. Further on before the procedure I stuck in now the OS has been Android 3.1
Hope those background information allows some more conclusions but
right now I am still trying to figure what kenfly ment by mentioning
>go into advanced and wipe dalvik cache
If I understand for example those guys http://forum.xda-developers.com/showthread.php?t=560207 right (hopefully it is allowed to put that link here) it seems to be a procedure before flashing a new ROM. What I am asking myself is do I right now not have a working one anymore? May be I misunderstood in the past but so far I thought the sequence is unlock> root> custom rom... and so far I think I am not successfully rooted yet so I wouldnt be supposed to flash a new ROM. So I think what I need to do now is to get my device successfully rooted before wiping the 'dalvik cache', am I wrong?
--
Cheers Michael
Click to expand...
Click to collapse
Did you flash the ClockworkMod recovery before rooting [after unlocking], and if so, which version?
If you don't have that installed, you wouldn't see the advanced option in the recovery menu.
You have a wifi model and I think the wifi hardware is all the same so you could flash the US Xoom system image and that should solve your access and updates problem, But since it's a HongKong Xoom, there may be some differences, so try it out but use caution.
hey guys looks as I dont get the message. I am still stuck at the recovery screen. I did
>go into recovery and wipe Everything/ factory reset, wipe cache
but whats next? Rebooting does not change anything, still the same logo screen only. So am I supposed to apply a proper image by 'apply update...'?
--
Cheers
You say you have a 3G Xoom - but the MZ606 is WiFi only.
Do you remember what image you applied to mess things up in the first place?
sure, the name is rootboot.img
It should be the one from 3*w.addictivetips.com, '/?attachment_id=45936'. I separated the link as I dont wanna mislead anyone here but I hope its still possible to follow up
--
Thanx for your help
-sorry for the 3G thing, no idea why I did type that. It definitely is a WiFi only
-and i idd not do any clockworld thing before or what ever. It has been just an ordinary MZ606 automatically updated to the 3.1 android version, but unlocked. For unlocking I used the android.sdk and typed the command to do so, thats everything I did before getting stucked with those rooting procedure
Hey guys dont leave me alone. I may tend to do another stupid thing ... well I am capable to find former posts about how to recover so on but as U asked some more details it seems to be depending on which exact device I have and what exactly I did before. So I hope U could still guide me to the harbor
hey.ur on 3.1 right?
I assume you have knowoedge on fasboot.
Find the appropriate boot.img for ur device then flash it via fasboot.
Maybe u flash the wrong boot.img
---------- Post added at 07:15 AM ---------- Previous post was at 07:11 AM ----------
Or go back to stock. http://developer.motorola.com/products/software/
well the problem (after data/factory reset and wiping cache) is the application (android.sdk) still cant find the device... I assume thats due to device still stuck at the M logo and I cant tpe in the WiFi password for example.
So how could I flash another ROM to the device without having the OS working on it properly?
[email protected] said:
well the problem (after data/factory reset and wiping cache) is the application (android.sdk) still cant find the device... I assume thats due to device still stuck at the M logo and I cant tpe in the WiFi password for example.
So how could I flash another ROM to the device without having the OS working on it properly?
Click to expand...
Click to collapse
Do you have the proper drivers installed? Make sure you get them from Motorola.
Your device should be seen if ADB and Fastboot are set up correctly.
Once you can see the device I would use fastboot to reinstall the proper image (again from Motorola - they will have the correct Image for your Chinese Xoom)
yes I do have the proper drivers from M and they worked perfectly before once I flashed the wrong image. May be my problem is too simple for U guys or as I am not capable to deliver appropriate information to get some help.
For my understanding it is obvious why my pc can't get the device as the device obciously cant get an wireless IP without knowing the WPA2 key and I cant type in the wireless key as the OS (on that device) does not fully start up. Which wireless device works without any basic configuration? So does mine I guess even though I am not expert... but even I deactivated any security measures on my router it still the device didn't connect (check only at the routers active device list)
Once again my question: How could I flash another ROM to the device without having the OS working on it properly? I think the OS is (part of) those wrong IMG i did flash before, so I assume I will never get it working
--
Regards
Can u go to fastboot?
When the xoom bootup press vol down immediately.it says starting fastboot etc.
If your pc can detect it then flash the correct images to ur xoom.
Btw lets talk on yahoo msgr. Pm me ur email.im free this time.
princenoob said:
Can u go to fastboot?...[/UOTE]
I keep he decvice at the recovery menu for 2 days now but yes I can "go to fastboot" too but again that doesnt change anything regarding connecting my device to the wireless router. Why none of U guys replies on those obvious fact? The XOOM like all other devices I know will not connect to any wireless hotspot without any confirmation (may be a password) on its UI and as I cant get into the UI...
May be its the wrong directory for thes question. Is it possible to shove to Q&A?
Click to expand...
Click to collapse
No no.why would you connect it on wireless router in the first place.connect it on ur pc! So if the pc detected it.then flash thru adb.
oh thanx for that hint. I thought it works only connected via wifi. Well now the SDK states a number instead of the device name or MZ606. I hope its not my HTC Desire but I did deactivate the wireless on there.
So if it really is the MZ606 (I can take the battery off the HTC just to make sure should I go back to the original image first, then install clockworld, then root?
--
thanx in advance
Sdk only detects devices connected to pc.so your phone has nothing to do with it.did u already download the firmware for ur xoom?the link i post awhile ago download the rom there.do you know how to flash it thru fastboot?.if yes then i think u can revive ur xoom.
---------- Post added at 10:30 AM ---------- Previous post was at 10:25 AM ----------
if you have ur original copy of ur boot.img then flash it.if not better flash from stock.the use this tutorial to root. http://forum.xda-developers.com/showthread.php?t=1242241
Please hit thanks if i help you in anyway.
[email protected] said:
oh thanx for that hint. I thought it works only connected via wifi. Well now the SDK states a number instead of the device name or MZ606. I hope its not my HTC Desire but I did deactivate the wireless on there.
So if it really is the MZ606 (I can take the battery off the HTC just to make sure should I go back to the original image first, then install clockworld, then root?
--
thanx in advance
Click to expand...
Click to collapse
[email protected], you seem to be lacking some very basic understanding of how all of this works on the Xoom. No wonder you felt frustrated.never in a million years would I guess you would try to flash an update or recover your Xoom via a wireless connection.
That said, hopefully you are now on the right track. I wish you good luck.
Sometimes my Nexus S (i9020) hangs on Google logo when booting. This happens let's say 5 of 10 times. However, once it's booted it works just fine.
I have been investigating what's causing it and I have a guess that it's because of internal SD card. But I'm not sure what exactly is wrong with it as mentioned everything works just fine if phone boots.
Why I think it's SD problem? I have tried to install another ROM using CW and when I chose to install zip from SD card, CW just reported that "Can't mount SD card" (something like this). I did couple of restarts and then it worked fine. So it seems to be that phone sometimes cannot mount or recogzine(?) SD card and that's why it hangs on Google logo.
Do you have any ideas what could be wrong with SD? It shouldn't be a contact problem as it works without any problems when phone is finally booted.
I have also tried to format/partition card, but it didn't help.
Someone please correct me if I'm wrong, but I don't think the Nexus S has any SD card. So that would make sense that it cannot mount what doesn't exist.
It has 16GB NAND memory which is basically the same thing as SD card. NAND is a technology used for USB drives, memory cards etc.
And regarding mounting, it says "can't mount" only like 5 of 10 times, other 5 times it works (mounts) perfectly.
xtasy55 said:
Sometimes my Nexus S (i9020) hangs on Google logo when booting. This happens let's say 5 of 10 times. However, once it's booted it works just fine.
I have been investigating what's causing it and I have a guess that it's because of internal SD card. But I'm not sure what exactly is wrong with it as mentioned everything works just fine if phone boots.
Why I think it's SD problem? I have tried to install another ROM using CW and when I chose to install zip from SD card, CW just reported that "Can't mount SD card" (something like this). I did couple of restarts and then it worked fine. So it seems to be that phone sometimes cannot mount or recogzine(?) SD card and that's why it hangs on Google logo.
Do you have any ideas what could be wrong with SD? It shouldn't be a contact problem as it works without any problems when phone is finally booted.
I have also tried to format/partition card, but it didn't help.
Click to expand...
Click to collapse
I have the same problem too. I've, yet, to find out the real cause. I want a warranty replacement unit but I know they are going to say that I'm OOW because it's unlocked.
You have to send it in.
I had this problem last week, after hours of searching the net, I found other people with this problem. Its nothing you can fix your self unless you can take apart your phone and replace the bad part. It really sucks to be without the nexus, but they got mine repaired, I am just waiting for them to send it back. Its says they had to "replace a bad component" on the repair ticket. Good luck.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
LordPhong said:
I have the same problem too. I've, yet, to find out the real cause. I want a warranty replacement unit but I know they are going to say that I'm OOW because it's unlocked.
Click to expand...
Click to collapse
Lock your boot loader before you send it in, very easy to do via ADB.
smoka206 said:
I had this problem last week, after hours of searching the net, I found other people with this problem. Its nothing you can fix your self unless you can take apart your phone and replace the bad part. It really sucks to be without the nexus, but they got mine repaired, I am just waiting for them to send it back. Its says they had to "replace a bad component" on the repair ticket. Good luck.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
Lock your boot loader before you send it in, very easy to do via ADB.
Click to expand...
Click to collapse
So, there's no flag somewhere saying that you unlocked your device? What did you tell them the problem was? Mine does it too often.
I'm seeing the same issue on my phone. It sounds like its SD card related but it has to be something with the connection since it only happens during boot time. Correct me if I'm wrong but android doesn't actually need SD card to boot so why would it have an issue. That's what makes me think its something else.
---------- Post added at 04:04 PM ---------- Previous post was at 04:01 PM ----------
LordPhong said:
So, there's no flag somewhere saying that you unlocked your device? What did you tell them the problem was? Mine does it too often.
Click to expand...
Click to collapse
If you can factory restore the phone and then lock it they have no way of knowing you had it rooted. Just make sure your SD storage is cleaned too.
Just wondering if anyone else had this issue and what they did to fix it.
Hi!
If you plan to go for repair your device , then it's no need relocked your bootloader . During the warranty period they will repair it for free.....
->just take a look at this : http://forum.xda-developers.com/showthread.php?t=1360146
.....to understand read all ....and now at this time my phone work very well
surdu_petru said:
If you plan to go for repair your device , then it's no need relocked your bootloader . During the warranty period they will repair it for free.....
->just take a look at this : http://forum.xda-developers.com/showthread.php?t=1360146
.....to understand read all ....and now at this time my phone work very well
Click to expand...
Click to collapse
Thanks but I don't think yours is a same issue. Mine is just stuck on the Google logo. However turning it off and plugging in the charger and there powering after the charge display usually fixes it.
Right now I'm up for more than 3 days without rebooting but I'm afraid that eventually it will go bad and not be able to boot properly.
Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz
Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...
Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz
Bootloader 70.13
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.
Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz
Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz
Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz
You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen
Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz
This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!
How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.
When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium
Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz
I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help
Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.
ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.
Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.
bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.
I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro
Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff
Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )
Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out
Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!
Hi,
This is my first time trying to root a tablet but managed to unlock the bootloader and install magisk + Edxposed, but was unable to find a module that enabled exfat for the sd card.
Currently it only reads Fat32 formatted cards but I would like to load a 10gb file on there that the device can read.
Any ideas how to go about this? will flashing a custom kernel/ rom help me with this?
All help is appreciated.
Thanks in advance!
rachelld said:
Hi,
This is my first time trying to root a tablet but managed to unlock the bootloader and install magisk + Edxposed, but was unable to find a module that enabled exfat for the sd card.
Currently it only reads Fat32 formatted cards but I would like to load a 10gb file on there that the device can read.
Any ideas how to go about this? will flashing a custom kernel/ rom help me with this?
All help is appreciated.
Thanks in advance!
Click to expand...
Click to collapse
I believe you'd need something like vold-posix, along with a version of magisk modified to inject it
But vold-posix is for Android 8.1, although I believe there is a modified 9 build for Pixels.
I'm not even sure if anyone has gotten any custom roms working on any of these yet, but if they have, might be your only option.
Thanks!
As of now I think I bricked it....
I messed around and accidentally erased the system partition, tried to fix it by flashing the image posted here (https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227) and now the screen won't turn on, no recovery mode, no adb..... the device is still detected through the SP flash tools though.
I think the image I used wasn't complete - can anyone upload a complete working image (including a scatter file) I don't care if it's stock or custom, just need something working on the device.
Thanks all!
rachelld said:
Thanks!
As of now I think I bricked it....
I messed around and accidentally erased the system partition, tried to fix it by flashing the image posted here (https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227) and now the screen won't turn on, no recovery mode, no adb..... the device is still detected through the SP flash tools though.
I think the image I used wasn't complete - can anyone upload a complete working image (including a scatter file) I don't care if it's stock or custom, just need something working on the device.
Thanks all!
Click to expand...
Click to collapse
Uploading my WWR backup right now. Kinda slow internet at work so I'll post the link tomorrow morning. Probably around 10am EST. It also has the scatter.
Edit: https://www.dropbox.com/s/pmgbaik485pa9st/ONN%2010KB%20Tablet%20ONA19TB007.zip?dl=0
razredge said:
Uploading my WWR backup right now. Kinda slow internet at work so I'll post the link tomorrow morning. Probably around 10am EST. It also has the scatter.
Click to expand...
Click to collapse
Thanks so much! Will try flashing this when I get home later today
rachelld said:
Thanks so much! Will try flashing this when I get home later today
Click to expand...
Click to collapse
Thanks for posting it, unfortunately it seems that my device was hard bricked and will not turn on anymore - even to the black screen I had before.
rachelld said:
Thanks for posting it, unfortunately it seems that my device was hard bricked and will not turn on anymore - even to the black screen I had before.
Click to expand...
Click to collapse
Is it still detected by the computer? That's really all you need to flash the ROM. I would be careful not to overwrite or format the unit-specific data on the emmc, like nvram, proinfo, persist, etc. I hope those did not get corrupted on your device.
rachelld said:
Thanks for posting it, unfortunately it seems that my device was hard bricked and will not turn on anymore - even to the black screen I had before.
Click to expand...
Click to collapse
Is your computer still detecting it? What specific errors is SFFT giving you? Did you follow the guide HERE?
Appreciate all the help here! I did follow that guide but I believe I messed up when I deleted the internal storage so the flashing did not work...
Either way I have another one to play with as these were super cheap on black friday - does anyone have any ideas for my original question?
I don't mind flashing a custom rom if anyone knows of one that works with this device.
@rachelld, I don't understand what you mean by "deleted the internal storage" (I don't think you can delete the emmc chip ), but these tablets are basically unbrickable as long as you have a backup or at least the device-specific areas remain in the ROM. There is also no secure boot to speak of.
@diplomatic Have no idea what I did but at one point I did hit a Chinese screen and clicked clear Emmc now that you mention it... (At least that's what Google translate told me it meant....)
I am left with a device that won't turn on at all, sp flash tools claims that it flashed successfully but still no response from the power button
@rachelld, what about connecting it to the wall charger?
diplomatic said:
@rachelld, what about connecting it to the wall charger?
Click to expand...
Click to collapse
Nothing doing, no sign of life. Tested the charger with another device to make sure it's working
rachelld said:
@diplomatic Have no idea what I did but at one point I did hit a Chinese screen and clicked clear Emmc now that you mention it... (At least that's what Google translate told me it meant....)
I am left with a device that won't turn on at all, sp flash tools claims that it flashed successfully but still no response from the power button
Click to expand...
Click to collapse
Well no, if you did erase the emmc, then the stock Rom backups shared will not have enough data for you to fully restore from.
And it is not know what partitions can be shared between devices. For example. Secro has device specific data on it. Nvram , also.
So if you have multiple devices. Follow the wwr readback process and fully read back all the partitions from one that works. And flash it back to the bricked one.
rachelld said:
@diplomatic Have no idea what I did but at one point I did hit a Chinese screen and clicked clear Emmc now that you mention it... (At least that's what Google translate told me it meant....)
I am left with a device that won't turn on at all, sp flash tools claims that it flashed successfully but still no response from the power button
Click to expand...
Click to collapse
That's the factory mode, the clear eMMC option should just be another factory reset option.