Related
Hi all, I just ordered a Chinese B63M phone at cect-shop.
Nice phone with great specs.
I alreadu know how to root it, but are there already custom Roms available?
Could'nt find a lot of info, just a Russion version.
B63M... thats my phone
Henkdrenth said:
Hi all, I just ordered a Chinese B63M phone at cect-shop.
Nice phone with great specs.
I alreadu know how to root it, but are there already custom Roms available?
Could'nt find a lot of info, just a Russion version.
Click to expand...
Click to collapse
Now that makes us 2 people who owns a B63M and got it from cect-shop.
What I find out about their phones is that it may not easily allow you to perform some insider operations, for instance, maybe its me but I could not find any custom recovery installed and this led to my first issue after I rooted, and installed the ROM manager, I saw the 'fix permission' and clicked it hoping to resolve my force close issues and it asked me to reboot after performing the process but it never got out of the boot, the loop continued, trying to boot into recovery become impossible but somehow a combination got me into a mode where I was able to clear flash and this took me back to a pre factory flash good thing I backed up titanium so I cld restore my apps and upgrade.
Right now I have tried to flash and the screen has gone blank yet the phone is responding to touch as I can hear sounds when the screen is clicked, indicating that its not bricked I just cant see anything going on (this is my current situation and seriously looking for help).
Lastly, I am trying to find out the htc equivalent to this b63m, it looks htc but I cant be sure which of the htc has been more or less cloned... this is going to help with a lot of things if known.
Cheers
Hi there,
If you are looking for a custom recovery, try this forum, altough you have to translate it because it is in German.
Lots of people there with our phone end they know how to get a custom recovery on it.
Cect is German
Henkdrenth said:
Hi there,
If you are looking for a custom recovery, try this forum, altough you have to translate it because it is in German.
Lots of people there with our phone end they know how to get a custom recovery on it.
Click to expand...
Click to collapse
Yeah thanks, I have also stumbled on the site forum before but I cld not get something out of it, maybe I have not taken time enough to search, I am back on it now and hope I get a solution to the blacked out screen problems I have after flashing.
You know cect-shop is German, they are a German company in China... I am talking to them on skype and hoping they can help me out but they seem pretty busy or cant be bothered because their response is so much delayed or even not at all.
Well technoforum has a special B63M section with all tools required.
They also have nice custom roms like a Cyanogen fork.
I also don't speak Italian, but with the help of Google translate I'm getting pretty far.
But I do let Google translate from Italian to English, that gives me the best result.
Good luck!!
Do you also get no working screen after a reboot with both volume + and power button?
That should get you to the recovery screen without any ROM drivers.
Very correct, no screen even in recovery
When I do the button combination, I believe that it may have responded to my combination for recovery mode but I just cant see anything on the screen, it just remains the same way it was... maybe it graphics issue, as in is the graphics is messed up for some reason or resolution issue, you wont see anything being displayed.
I am just guessing here but all I did was to simply flash an update.zip from sd card.
That is very strange, since flashing a rom does not affect the screen of the recovery boot.
The rom video driver gets only active during the boot process of the rom.
In the past I had some boot problems with my Wildfire start-up that I solved by removing the SIM card and SD card, removed the battery for some minutes and them booted completely resetted.
You could try that, if that does not solve the problem, the only way to wipe the phone back to factory-reset is doing it blind.
After I get my phone I could make a step-by-step guide so you could get to the reset menu...
Another possibility is to re-flash a fresh recovery img to the phone. Since I don't know what was in your update.zip, you could messed up the recovery menue, or even the bootloader.
Re-flashing those could also help and you don. t need the display from the phone, since you use the PC for that.
Here it is
Here is the update.zip I flashed. http://chinamobiles.org/downloads.php?do=file&id=618&langid=4
I am a bit surprised myself that the screen is blanked out but the phone seem to be working still.
I have removed both SIMS and SD card plus battery several times etc. nothing changed.
You said ''After I get my phone I could make a step-by-step guide so you could get to the reset menu...'', I hope you get your phone soon tho, and i can see the step-by-step guide you made.
I have actually flashed recovery into it using flash tool, ODIN dont seem to see the phone (at least the yellow box saying COm4 or 5 is not showing), I can see the phone using adb but when I say adb reboot download or recovery, something happens but I cant see what it is.
I too have a B63M...!!! Spice Mi-350n...........
If you need a moded recovery, i can port it for you........but you need to follow some instructions...i'll give them tomorrow!!
Waiting on you... I hope my blank screen gets sorted.
balamu96m said:
I too have a B63M...!!! Spice Mi-350n...........
If you need a moded recovery, i can port it for you........but you need to follow some instructions...i'll give them tomorrow!!
Click to expand...
Click to collapse
Ahh thanks man... Ii will wait to hear from you tomorrow, I aim in UK and depending on what time zones you are in but I hope to find you online to connect again.
I hope you have understood my particular issue here tho, the screen if blank even tho the fone seem to be alive and it follows the boot sequence, I can even find it using 'adb devices' command, it just the screen gone blank.
Someone suggested it may be the boot.img but I dont know about that.
Cheers
I'm from India - Local time here is GMT+5:30......!!
So, here you go !!
B63M= MTK6573 + 650mhz + Android 2.3
So, one modded recovery.img can't be used for every B63M.......this is because a different B63M phone will have a different recovery.img..........(hope u understand)
Backing up everything:
1) ROOT is necessary. It is recommended to put the phone in 'Airplane mode' so that it won't disturb the process and make sure you have ~500 mb space in SD card.
2) Download 'BackUpTools.rar' from HERE and extract it to your SD Card. You'll have 2 folders - 'gscript' and 'Install'.
3) Install 'GScriptLite.apk' from gscript folder.
3) After installation, open the 'GScriptLite' application -> Menu -> Add Script.
4) Tick 'Needs SU ?'
5) Click 'Load File' and select 'Back23.sh' and then select 'save'
6) Now Click on 'Back 23' and Super User will ask for Permission and allow it. Nothing more to touch. Wait for few minutes. After few mins, it will say 'Auto Close is Cancelled'. Now its safe to close.
7) Your Back-Up will be in 'backup_' folder located in your SD card's root.
It will have files named ' firmware.info, preloader.img, nvram.img, seccnfg.img, uboot.img, boot.img, recovery.img, secstatic. img, misc.img, logo.img, expdb.img, cache.img, system.img, data.img' in that folder. Copy it to your computer and keep it at a safe place. More Over if you are posting in the forums or sharing it online, don't include ' data.img, cache.img and nvram.img' as they contain your personal information.
Here i need two files.One is recovery.img and the other is firmware.info.
If you give both, i can port one for your phone !! Also mention your phone's model name/number because, without that it is not possible.
xdadeem said:
Here is the update.zip I flashed. http://chinamobiles.org/downloads.php?do=file&id=618&langid=4
HTML:
I am a bit surprised myself that the screen is blanked out but the phone seem to be working still.
I have removed both SIMS and SD card plus battery several times etc. nothing changed.
You said ''After I get my phone I could make a step-by-step guide so you could get to the reset menu...'', I hope you get your phone soon tho, and i can see the step-by-step guide you made.
I have actually flashed recovery into it using flash tool, ODIN dont seem to see the phone (at least the yellow box saying COm4 or 5 is not showing), I can see the phone using adb but when I say adb reboot download or recovery, something happens but I cant see what it is.
Click to expand...
Click to collapse
That was the problem, you flashed only the update, not a complete Rom.
I suggest you make a complete re-flash vorm scratch, so refash a fresh recovery.img and re-flash als a new Rom.
You can vind one at technoforum' as earlier mentioned
I thot you shd read my latest.
Ok guys I appreciate this a lot.
Here at this point I think you shd hear my developments before taking any further actions or suggestions.
aha thanks, I did just that and it worked although it is still blank at the beginning of boot but later something shows up on screen and completes boots.
Remember I mentioned that someone suggested it might be a boot.img problem... well, I used flashtool to flash a boot image and I can say it worked, I now have the visuals, even tho the screen is still blank at boot start but soon after it picks up and its working, now I have the phone again.
so @balamu96m, my issue was basically the screen, without seeing anything I cannot follow the back up suggestion you gave me here, but now I can see it again.
A couple of additional issues tho...
1- I checked the kernel and it has changed from 2.3.5 into 2.3.4 and >In the current ROM flash I have lost a couple of capabilities like Flashlight, camera etc
2- I followed this link http://www.technoforum.it/forum/viewtopic.php?f=73&t=3351 to flash recovery and it says Successful with the green Circle -OK-... but I still cant get boot into recovery either when I use the keys combi or when I try to boot into recovery in mobileuncle tools, it just goes blank and stays like so until I have to remove the battery and restart boot normally.
3- From the same link above they have the Golight ROM in part 2 after recovery in part 1, I am assuming this a good ROM to flash and the things I lost will get back, but I still cant boot into recovery.
Coming back to the response from balamu96m... Should I still go ahead with what yu suggested and provide you the files details you want? both recovery.img and firmware.info... I am asking because I no longer have the original ROM that came with the phone and like I said I cant even get into Recovery after I tried flashing a new recovery.img, this one from the same link above (see the recovery.img inside the 'Recovery Moddata' file from the 'UPDATEB63MRecovery2012' download file.)
Great to hear that you have visual again!
You still have root yes?
The golight rom from technoforum is a good one.
I expect mine any moment now so I can customize mine too.
Good luck!
xdadeem said:
Ok guys I appreciate this a lot.
Here at this point I think you shd hear my developments before taking any further actions or suggestions.
aha thanks, I did just that and it worked although it is still blank at the beginning of boot but later something shows up on screen and completes boots.
Remember I mentioned that someone suggested it might be a boot.img problem... well, I used flashtool to flash a boot image and I can say it worked, I now have the visuals, even tho the screen is still blank at boot start but soon after it picks up and its working, now I have the phone again.
so @balamu96m, my issue was basically the screen, without seeing anything I cannot follow the back up suggestion you gave me here, but now I can see it again.
A couple of additional issues tho...
1- I checked the kernel and it has changed from 2.3.5 into 2.3.4 and >In the current ROM flash I have lost a couple of capabilities like Flashlight, camera etc
2- I followed this link http://www.technoforum.it/forum/viewtopic.php?f=73&t=3351 to flash recovery and it says Successful with the green Circle -OK-... but I still cant get boot into recovery either when I use the keys combi or when I try to boot into recovery in mobileuncle tools, it just goes blank and stays like so until I have to remove the battery and restart boot normally.
3- From the same link above they have the Golight ROM in part 2 after recovery in part 1, I am assuming this a good ROM to flash and the things I lost will get back, but I still cant boot into recovery.
Coming back to the response from balamu96m... Should I still go ahead with what yu suggested and provide you the files details you want? both recovery.img and firmware.info... I am asking because I no longer have the original ROM that came with the phone and like I said I cant even get into Recovery after I tried flashing a new recovery.img, this one from the same link above (see the recovery.img inside the 'Recovery Moddata' file from the 'UPDATEB63MRecovery2012' download file.)
Click to expand...
Click to collapse
You flashed a recovery, but that is not working ah?? Oh God!!
Why did you do that bro??
Do you have any backup of the stock one??
If you dont have, then i have 2 ideas....one idea is to flash something else such that your fone won't boot....now you can send your phone back to the manufacturer and ask them to reflash everything!!!
The other idea, i'll tell you after sometime!!
It was always so
balamu96m said:
You flashed a recovery, but that is not working ah?? Oh God!!
Why did you do that bro??
Do you have any backup of the stock one??
If you dont have, then i have 2 ideas....one idea is to flash something else such that your fone won't boot....now you can send your phone back to the manufacturer and ask them to reflash everything!!!
The other idea, i'll tell you after sometime!!
Click to expand...
Click to collapse
The reason i flashed recovery initially was that my phone went into a boot loop and I was unable to get into recovery, after a while somehow i figure it out and cleared flash and then restored my phone apps and co and got on fine.
But if I could not get into recovery it means that there was not stock recovery on my phone or it got missing somehow. This I have to ask Henkdrenth since he is getting the same phone from the same shop too, but there was no recovery in my B63m, I already heard there is a recovery problem with the phone anyway, and thats why I flashed recovery and it worked but then I flashed ROM and the screen went blank, which is what got me to this forum.
I did not just go and flash recovery, it because there was none on the phone in my opinion.
xdadeem said:
The reason i flashed recovery initially was that my phone went into a boot loop and I was unable to get into recovery, after a while somehow i figure it out and cleared flash and then restored my phone apps and co and got on fine.
But if I could not get into recovery it means that there was not stock recovery on my phone or it got missing somehow. This I have to ask Henkdrenth since he is getting the same phone from the same shop too, but there was no recovery in my B63m, I already heard there is a recovery problem with the phone anyway, and thats why I flashed recovery and it worked but then I flashed ROM and the screen went blank, which is what got me to this forum.
I did not just go and flash recovery, it because there was none on the phone in my opinion.
Click to expand...
Click to collapse
Now, is the recovery working??
Does the phone boot properly??
Wrong section. Moving to general.
YES and NO
balamu96m said:
Now, is the recovery working??
Does the phone boot properly??
Click to expand...
Click to collapse
After many troubles, I found a mod for w690 which is the build version of my phone, I could not boot to recovery so used flashtool and when I load the scatter text of the one I found, it automatically load in every item on the list including recovery and boot img , etc, so I flashed these to my phone... and for the first time I was back in how the phone came to me,
Gingerbread has now returned to 2.3.5.
One thing I have noticed is that the phone freezes on me and then reboots?
I still cannot boot into recovery, I tried this again using mobileuncle tools...
It seem that I have flashed my phone which is good, but I was unable to wipe cache because I could not boot into recovery to do this which may be the source of the current freeze and reboot.
Can I solve this using the mobileuncle or what can I do to wipe cache, if that is the problem
Well, received mine, rooted it an flashed a new recovery from technoforum using myuncletools.
All went well, so I suggest you do also a fres re-flash with a proper recovery.
Hope that should solve your problem.
Edit: moved from my tablet to my PC to look for the link of a correct recoveryfile for you.
First, load this recovery.
Unpack it and put the content to the root of your SD card.
Use myuncletools to flash this recovery.
Now you should have a usable custom recovery that allows you to factory-reset and wipe your phone
Install a fresh rom
How to? Look here
Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?
Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .
As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know
Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk
Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!
nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.
Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please note I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronize me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image. Any help or suggestions would be very much appreciated.
Carbon131 said:
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please not I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronage me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image flashed. Any help or suggestions would be very much appreciated.
Click to expand...
Click to collapse
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
polobunny said:
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
Click to expand...
Click to collapse
Hopefully someone may know what to do.
Carbon131 said:
Hopefully someone may know what to do.
Click to expand...
Click to collapse
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
polobunny said:
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
Click to expand...
Click to collapse
Yeah I can't seem to do that.
Carbon131 said:
Yeah I can't seem to do that.
Click to expand...
Click to collapse
Make sure your cable is connected when you try to put your phone in download mode. Turn off the phone, then hold both volume + and -, and press power. Continue holding volume buttons until you see download mode.
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
JunoZXV said:
Basically I was using TWRP to wipe my TF700T and I wiped the OS. Luckily I made a recovery on my SD, but the problem is that I can't get it to boot back into TWRP in order to run it. All the Power + Volume Down does is just cause the device to rumble. Powering on the device just lets it sit in the bootscreen. If I can get into the bootloader I can basically fix the machine. Problem I have remaining is that I can't seem to get into the bootloader.
The device calls itself APX when plugged into my computer now, if that means anything. I'm gonna try to drain the battery by leaving it on over night without the flash card. Maybe that'll do something.
Any suggestions on how to unbrick this thing? Or did I just succeed in turning a very expensive tablet into a very expensive paperweight?
Click to expand...
Click to collapse
Im having exactly the same problem, did you find a solution to this?
So far no results yet. I tried hitting the reset button on the side but all that did was lead me back to the boot screen. I read something about undoing the the hard boot using a series of override programs. But the problem is the documentation is so cluttered that I can't fathom the instructions (I'll try it again just in case.)
Bump update: So I called Asus and it turns out it's gonna cost 288$ to get the thing fixed by them. So I'm not doing that. I'm looking into other ways of recovery. I've got other multiple options I'm exploring at the moment. Like looking for a recycling program or a way to use the technology in a new way.
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
JunoZXV said:
UPDATE X2
So I talked to a friend and the very fact that it sits at APX was a tipoff. Basically it means the recovery is shot but the Bootloader is OK. Meaning that the device isn't as bricked as I thought. What needs to be done is to download the android ADT bundle (google it) and from there get into the platform tools under command prompt, type "adb" then "adb devices" and finally "adb reboot recovery"
if it works the recovery should reflash and then using the backup restore the OS.
Granted I'm having trouble getting my comptuer to say "APX has been connected" due to a faulty data cable but I should be home free after this
Click to expand...
Click to collapse
Unfortunately if you can only get to APX mode and you don't have nvflash specific blobs for your device you are hard bricked...
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
Sorry it really doesn't look good, Maybe i can corrected but the device will fallback to APX mode if the bootloader is corrupted, without a bootloader you cant install/fix a recovery and without NvFlash blobs you cant fix the bootloader. Your two options are buy a new motherboard and replace it yourself or send it in for repair with Asus
JunoZXV said:
Luckily I make a recovery file in my SD card wayy back when I did my first Cromi mod. It should still work if the forced recovery restores TWRP. Otherwise, yes, I might be hard bricked.
My friend, however, thinks there might be another way to force a OS past this block though. I'll have to see how this plays out.
Click to expand...
Click to collapse
As JTR says I'm pretty sure you can't fix this without replacing the hardware now. I don't think your friend really understands what APX mode is. YOu can't access the bootloader nor recovery. Without NVflash backup blobs you can't recover anything, there is no way to get your TWRP backups back on to the device and even if you could you have no working bootloader......
So, I wanted to go to the newly released snapshot of CM12, so I decided to update my TWRP as well. Turns out, that was a terrible mistake, because not only did it not work (so I can't go into recovery), but I believe I soft-bricked my phone, because I cannot boot into it regularly. I can still go into the bootloader (which means I can use ADB), but that's it. Hitting recovery in the bootloader is an infinite screen, and booting regularly is an infinite screen. I followed this video: https://www.youtube.com/watch?v=9HWj_1KHbuY . After it didn't work, I did a command that cleared the cache of my phone, and tried the same thing again. Now my phone is not working, and I'm going to cry myself to sleep. Please help.
Right now I am on a Mac that I've never used ADB on before, so it doesn't recognize my phone, so I cannot use it. If there is a way around confirming the ADB connection from my phone and forcing ADB to work with it, that would be good to know. I will be back to my PC that knows my phone on Sunday, so I can do that then.
Is an RUU the best thing to do? I'm fine with losing everything on the phone.
Hmm i installed the latest verison of twrp with my mac via fastboot ( followed directions from twrp site for the commands). I would try to get adb/fastboot to work on your mac first and maybe try to fastboot flash twrp again? and if that does not work i would just do a RUU honestly, but i'm sure someone smarter than me can chime in and get it resolved . For instructions to install adb/fastboot on a mac i followed this http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/ If it does not recognize your device try installing htc sync manager.
darthnix said:
So, I wanted to go to the newly released snapshot of CM12, so I decided to update my TWRP as well. Turns out, that was a terrible mistake, because not only did it not work (so I can't go into recovery), but I believe I soft-bricked my phone, because I cannot boot into it regularly. I can still go into the bootloader (which means I can use ADB), but that's it. Hitting recovery in the bootloader is an infinite screen, and booting regularly is an infinite screen. I followed this video: https://www.youtube.com/watch?v=9HWj_1KHbuY . After it didn't work, I did a command that cleared the cache of my phone, and tried the same thing again. Now my phone is not working, and I'm going to cry myself to sleep. Please help.
Right now I am on a Mac that I've never used ADB on before, so it doesn't recognize my phone, so I cannot use it. If there is a way around confirming the ADB connection from my phone and forcing ADB to work with it, that would be good to know. I will be back to my PC that knows my phone on Sunday, so I can do that then.
Is an RUU the best thing to do? I'm fine with losing everything on the phone.
Click to expand...
Click to collapse
You could go find the ruumode-flashable recovery that I think is in one of dottat's ruu threads (5.0.1 one I think). Then change the name of the file to 0p6bimg.zip and flash it in bootloader. That should flash twrp to a phone without adb/fastboot.