After a failed OTA update, my iconia a500 stock (never rooted) bricked. Got CWM v5.0.2.3 installed through APX mode and the recovery mode starts pretty smooth when I boot with Vol DOWN + Power.
I can install every ROM (custom and stock) I could lay my hands on, ranging from 3.0.1 to 4.0.*. Also did the wipes in all imagined combinations: before installing a rom, right after installation (before first boot) and also after 1st boot attempt. Also made sure to format /data, /cache, /system and so on before every installation. Tried different SD cards and also a USB mass storage thumb drive.
The thing I just can´t explain yet, is how on every try the same thing happens, 1st boot (long one) seems to just fail and my tab gets back to that screen where you see the clock on the lower right and the pulley icon saying "Android System" on the upper left corner. After that, every boot does that and the Android initial setup screens never comes up.
Every rom I try delivers the same result, even though I get their splash logos (ephiphany, taboonay, thor) and all seems to be going OK, it always gets back to that "Android System", no error messages, nothing.
I found out that Thor rom 14.2 made the "Android System" screen touch responsive (no other did that), I can touch the clock, open the first level of settings and if I try to drill down, touching storage for an instance, it won´t load the app/menu, it gets righ back to the good old "Android System" screen.
After a custom rooted rom gets installed and I get the "Android System" screes, adb works fine and I manage to get in the tab with a shell, mount an SD card, use the ps command to see the process running and even start the bootanimation myself, so I´m assuming that android is runing OK, at least on the background. Adb also allows me to push files and install apks normally. Have some linux background myself, used the shell to browse around and checked some of the logs, nothing clear showing an error that would force my boots to terminate sooner.
Wondering if anyone experienced something like that and could point me at some direction. Am I missing something here ?? Thanks guys and great job i might add.
Still no luck ...
Hi everyone, wanted to get back and maybe share my logcat and bugreport retrieved by adb shell. If any of the more experienced members could take a look and point me to some direction, I´d really appreciate. Really i´ve tried all the methods arround here and other forums to unbrick it, it behaves and responds as if everything was OK and still fails to boot for the first time, even though, the system appears to be running ok on the backgroup the initial setup wizar never comes up and I get the "Android System" dreadfull screen.
Discovered that once in with adb shell I can run the setup wizard (calling it by prompt: am start -a android.intent.action.MAIN -n com.android.setupwizard/.SetupWizardActivity), but it only stays opened for a couple of seconds and never finishes its business, it just abends.
Not sure if this would be the proper thread to post, it would be great if someone could adivise where would be a proper place.
Thanks for your time.
Hi vortex,
Were you able to fix that? I'm having the exact same problem. :-(
I've been trying for days already.
Cheers,
Ok, here's the deal.. I have the Skyrocket, and a couple days ago, I accidentally stepped on it and cracked the screen. It no longer showed any picture, so.... In a fit, i threw it at the wall and shattered the screen completely. The phone still powers on, and boots to CM10 (I can hear the sound when I press the power/lock button). I have CWMR installed as well. Apparently, I didn't have USB debugging enabled (altho i could have sworn I did!), and now I can't get at any of my files from my sdcard.
I tried adb and fastboot, neither even detects the phone as being there.
I have a replacement device coming in a few days (AT&T insurance, GREAT STUFF!), so I would really like to be able to get my stuff from this phone ASAP... Anyone know a way?
Fastboot doesn't work?? Then something is wrong beyond just the screen. . . . Anyways, Can you boot into recovery?? If yes, there is a guess work method to mount the system partition via CWM so you can use adb. You can ask someone who uses the similar device with cyanogenmod10 to count the number of steps to go to the "mounts and storage" option in the CWM main menu and counts the steps to go to "mount system" option in the sub menu and use that counts to mount your system partition. . . . If you can successfully mount system partition then you can gain access to adbd (adb daemon) binary in your system partition and use adb from recovery just by plugging the device to your computer. And use adb shell to mount the other partitions and pull all the files you need. . . . I don't know whether if this works practically but theoretically it should work . . . . Keep in mind that you have to guess the no of steps carefully or else you may end up "wiping" any partition accidentally. . . .
#pitchblack5691#
i made the same mistake at one point lol try this it worked well for me when i couldnt even see the screen maybe it might work for you good luck http://code.google.com/p/adb-file-explorer/
pitchblack5691 said:
Fastboot doesn't work?? Then something is wrong beyond just the screen. . . . Anyways, Can you boot into recovery?? If yes, there is a guess work method to mount the system partition via CWM so you can use adb. You can ask someone who uses the similar device with cyanogenmod10 to count the number of steps to go to the "mounts and storage" option in the CWM main menu and counts the steps to go to "mount system" option in the sub menu and use that counts to mount your system partition. . . . If you can successfully mount system partition then you can gain access to adbd (adb daemon) binary in your system partition and use adb from recovery just by plugging the device to your computer. And use adb shell to mount the other partitions and pull all the files you need. . . . I don't know whether if this works practically but theoretically it should work . . . . Keep in mind that you have to guess the no of steps carefully or else you may end up "wiping" any partition accidentally. . . .
#pitchblack5691#
Click to expand...
Click to collapse
No, fastboot doesn't work either, I tried that as well... I was trying to get into recovery, I found another thread here that was an HTC phone, I think, with a similar issue. It gave steps for navigating CWM. I couldn't get the partitions to mount.
I think you're right, that there is something more wrong with it than the screenm, because in the Windows device manager, I could see 2 extra drives that were both listed as Samsung something (it's the next morning now), both with a size of 0 bytes. The strange thing is that the phone would boot. Completely boot. I had a friend message me on Fcebook, and the notification went off on my phone at the same time it did my loaner. (both of which were signed into my Facebook)...
crashpsycho said:
i made the same mistake at one point lol try this it worked well for me when i couldnt even see the screen maybe it might work for you good luck http://code.google.com/p/adb-file-explorer/
Click to expand...
Click to collapse
Thanks for the tip, but this didn't work either.. I don't know what else I screwed up on this phone, but wow... lol
PLEASE HELP!!! My tablet has been bricked and i will explain.First of all i rooted my device with CWM and then i read on a blog about being able to change the pixel density and so i download it and i remember when i first launch the app it says warning "Do at your own risk" and so i change the ppi from "216" to about 320 ppi, yeah thats!!!And since i have titanium backup installed it says "the device needs to reboot in order for changes to take effect"and i press allow. So i reboot the device and then wait for it to turn on, and no chance to turning on. So i try pressing the
POWER BUTTON + Both (+) (-) and says "Updating... Please do not press any keys!" and then back on the black screen, i assume its still on because its lit on the black screen, but does not want to function, but don't no why.Its obviously bricked and when i go to recovery mode by
pressing POWER BUTTON + VOLUME (-) and when i was on that screen i wiped the User data and the Cache Partition and wiped the
Dalvik cache, and then Press "Reboot System" and goes to the black screen.
Fastboot does not work, but instead gets stuck on the green words "FASTBOOT",only Recovery mode works.I know for fastboot it is
POWER BUTTON + VOLUME (+) . I'm stuck, i've used nexus 7 ToolKit, even if its for nexus 7 i tried because i'm eager to get the tablet unbrick.It almost worked for me but not well good with that program, Im not even sure if Nexus 7 ToolKit functions with Sero 7 Pro. But maybe you can answer that. I don't know how to download adb, i think it has to do something with the Path system variable, now i've caused another problem:crying:. WTF!!! I backspaced the path variable and now its empty, is there any way to bring it back to the original "Path" or replace it for another Path variable.
Anyways,i tried DPI changer and it changes the density back to the current ppi "216". Does not recognize the device.So that does'ent work.And now the only thing i havent tried is inserting the following " >su #mount -o rw,remount /system #chmod 644 /system/build " in ABD,but dont have abd.PLEASE GIVE ME ANY SUGGESTIONS TO WHAT I CAN DO!!! BUT NOT "WHAT I CANT DO".
Also is there any place i can take the tablet to repair in.
sent to supplier for warranty claim if possible ... then promise urself do not do any stupid on ur beloved tabs / any gadgets anymore to avoid this mess agn
desmondtee88 said:
sent to supplier for warranty claim if possible ... then promise urself do not do any stupid on ur belove
Click to expand...
Click to collapse
Xboxexpert
Xboxexpert helped me fix the tablet And i thank him with a $17.He is a really good guy and is the best i meet,he made my day!
Xboxexpert Youtube channel:http://www.youtube.com/user/xboxexpert
forum:http://forum.xda-developers.com/member.php?u=557282
website:http://thexboxexpert.com/
If you need help, Subscribe and follow on his threads
Xboxexpert: is the expert
Also If you want to donate to him and he will give assistance to you on the android devices.So go right now and check the threads and posts.Hes very helpful
Hallo,
being new to this forum and also new to Android devices, please feel free to move my post into the correct section of the forum if I used the wrong one. The use of the search function is also not unknown to me, however I may not know all terms to be used (rookie) and english still is a foreign language for me.
Anyway, I have a serious problem with my brandnew Jiayu G4T phone and at least I need some help in sorting my thoughts and ideas after several days of browsing through the community.
What I know for sure:
Phone starts booting but stops on the third screen (1st: Jiayul ogo white, 2nd: Jiayu logo green falling in place, 3rd: Jiayu logo white fading).
I am able to boot into stock recovery and into factory mode (mostly chinese characters).
I have access to my phone by adb shell and can look into the directories.
The event occured after an overnight update with weird behavior of the phone (what happened is posted in the assumption section, it was still pretty early and I was clearly not fully awake.
I had the Xposed framework and XPrivacy installed and running. All other apps were pretty common.
In ADB my phone is listed as 0123456789ABCDEF (weird number)
What I do not know / Assumptions:
In /data I see plenty of files telling me that the data wipe from recovery was not successfull, the data belong to previously installed apps.
It seems that I was able to flash a new ROM, in system/app I do not see any of my previously installed apps. Superuser.apk is still present.
I also can access data however only after using su in shell.
I cannot delete the data using rm or wipe data being in [email protected] #, I have no idea why. Read only....
SP Flash tool told me that the flash of the new ROM was successful (red, pink, yellow progress bar followed by green circle). I think that is a good sign.
I also was able to apply ADB sideload for installing a new ROM and the phone told me I was successful. Not sure if this is true considering that my phone still is not booting.
After finding my phone in the morning mobile connections were both down, I think that an Android update was not successful and it might have happened that I restricted this very app with XPrivacy inadvertently.
The phone identifier seems to tell me that XPRivacy might still be active somewhere....
What I think about the next steps:
I think that getting rid of the old data might be the key for success, but I have no idea HOW....
Any thoughts from your side re highly appreciated,
Thomas
Tomcat117 said:
Hallo,
being new to this forum and also new to Android devices, please feel free to move my post into the correct section of the forum if I used the wrong one. The use of the search function is also not unknown to me, however I may not know all terms to be used (rookie) and english still is a foreign language for me.
Anyway, I have a serious problem with my brandnew Jiayu G4T phone and at least I need some help in sorting my thoughts and ideas after several days of browsing through the community.
What I know for sure:
Phone starts booting but stops on the third screen (1st: Jiayul ogo white, 2nd: Jiayu logo green falling in place, 3rd: Jiayu logo white fading).
I am able to boot into stock recovery and into factory mode (mostly chinese characters).
I have access to my phone by adb shell and can look into the directories.
The event occured after an overnight update with weird behavior of the phone (what happened is posted in the assumption section, it was still pretty early and I was clearly not fully awake.
I had the Xposed framework and XPrivacy installed and running. All other apps were pretty common.
In ADB my phone is listed as 0123456789ABCDEF (weird number)
What I do not know / Assumptions:
In /data I see plenty of files telling me that the data wipe from recovery was not successfull, the data belong to previously installed apps.
It seems that I was able to flash a new ROM, in system/app I do not see any of my previously installed apps. Superuser.apk is still present.
I also can access data however only after using su in shell.
I cannot delete the data using rm or wipe data being in [email protected] #, I have no idea why. Read only....
SP Flash tool told me that the flash of the new ROM was successful (red, pink, yellow progress bar followed by green circle). I think that is a good sign.
I also was able to apply ADB sideload for installing a new ROM and the phone told me I was successful. Not sure if this is true considering that my phone still is not booting.
After finding my phone in the morning mobile connections were both down, I think that an Android update was not successful and it might have happened that I restricted this very app with XPrivacy inadvertently.
The phone identifier seems to tell me that XPRivacy might still be active somewhere....
What I think about the next steps:
I think that getting rid of the old data might be the key for success, but I have no idea HOW....
Any thoughts from your side re highly appreciated,
Thomas
Click to expand...
Click to collapse
This is your solution right here (hopefully)
1) If you have not installed the drivers, download, unpack and install drivers http://uloz.to/xwWU1vKw/mtk6589-driver-zip.
2) Download and unpack Stock ROM http://www.ejiayu.com/en/News2-1-100.html.
3) Download and unpack FlashTools http://uloz.to/x6U5ZDKs/spflash3-1316-0-150-zip, and Click on Flash_tool.exe.
4) Click button "Scatter-loading" and select a the MT6589_Android_scatter_emmc.txt in ROM.
5) Turn off your phone and remove the battery!
6) Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
7) The process will start and a red progress bar will appear after color purple, yellow. And green circles display. Finish. You can now safely disconnect your phone and turn it on.
Egbert
jimmys01 said:
This is your solution right here (hopefully)
Click to expand...
Click to collapse
This actually is a thread I found very early and unfortunately it was not working.
Honestly I assume that Isomehow lost root: How does this sound in the view of my observations and assumptions?
Thomas
It's my sister's phone and I don't know What she did exactly all she said that she tried to install candy crush from google play and then the problem begun each time the mobile reboots after 5-8 seconds I get a ton of stopped working notifications mainly about google apps like "error com.google.process.gapps has stopped" which repeatedly appear each time I press OK and a ton of other stopped working errors like weather,settings and anything I try to open. No matter what I do uninstall any app, change settings, change wallpaper after reboot everything revert back I tried to wipe/factory reset but no dice, I tried to flash the stock rom using SP flash tool and flashed the rom successfully but nothing changed the same apps the same wallpaper I am not talking about the default apps and wallpaper no I am talking about the apps that my sister installed before like Facebook, whats app etc...
I thought about flashing a custom rom and picked one but it required custom recovery which in turn required root access I tried several programs like kingroot, oneclickroot through PC but didn't work then I tried to flash CWM recovery through SP flash tool following the instructions I found here http://forum.xda-developers.com/showpost.php?p=61359133&postcount=4 and again the recovery was flashed successfully but when I tried to go to recovery I found the stock recovery instead I tried to flash the recovery using Fastboot but Fastboot came up with this error:
"FAILED (remote: partition 'recovery' not support flash)" which when I looked around turn out to be an error related to locked bootloaders but as far as I know the bootloader on Huawei y520-u22 is unlocked but wanted to make sure so I tried this command "fastboot oem device-info" but it gave me ... as in processing and nothing for a very long time until I gave up and closed the cmd. I then tried to boot into safe mode after pressing the power button then tabbing the shutdown option and selecting boot into safe mode but the phone rebooted into normal mode as usual.
and now I am out of options what should I do ?
Edit: eventually I found that my problem like this guy http://forum.xda-developers.com/showthread.php?t=895628 was that the \data partition is read only but I can't fix it the way he did since he used advanced partitioning in clockworkmod recovery but I can't flash it or any other custom recoveries.
mostafa_0017 said:
It's my sister's phone and I don't know What she did exactly all she said that she tried to install candy crush from google play and then the problem begun each time the mobile reboots after 5-8 seconds I get a ton of stopped working notifications mainly about google apps like "error com.google.process.gapps has stopped" which repeatedly appear each time I press OK and a ton of other stopped working errors like weather,settings and anything I try to open. No matter what I do uninstall any app, change settings, change wallpaper after reboot everything revert back I tried to wipe/factory reset but no dice, I tried to flash the stock rom using SP flash tool and flashed the rom successfully but nothing changed the same apps the same wallpaper I am not talking about the default apps and wallpaper no I am talking about the apps that my sister installed before like Facebook, whats app etc...
I thought about flashing a custom rom and picked one but it required custom recovery which in turn required root access I tried several programs like kingroot, oneclickroot through PC but didn't work then I tried to flash CWM recovery through SP flash tool following the instructions I found here http://forum.xda-developers.com/showpost.php?p=61359133&postcount=4 and again the recovery was flashed successfully but when I tried to go to recovery I found the stock recovery instead I tried to flash the recovery using Fastboot but Fastboot came up with this error:
"FAILED (remote: partition 'recovery' not support flash)" which when I looked around turn out to be an error related to locked bootloaders but as far as I know the bootloader on Huawei y520-u22 is unlocked but wanted to make sure so I tried this command "fastboot oem device-info" but it gave me ... as in processing and nothing for a very long time until I gave up and closed the cmd. I then tried to boot into safe mode after pressing the power button then tabbing the shutdown option and selecting boot into safe mode but the phone rebooted into normal mode as usual.
and now I am out of options what should I do ?
Click to expand...
Click to collapse
Hmm...
First, tell her to quit using Facebook app, Facebook Messenger, WhatsApp and other social media and texting apps. I know she just HAS to keep up with all her friends and the latest gossip but her device can't handle all those system demanding apps, they are literal HELL on mid-low end devices. They all constantly run scanning for updates and notifications, CONSTANTLY. They are notorious for making devices act crazy, especially when you have more than one of them.
For Facebook, its best to bookmark the Facebook page in mobile browser then create a shortcut for that bookmark on her homescreen, then it has to be set so that it loads the desktop site for Facebook, then she can view her Facebook messages, if it isn't set to load desktop site it will request she install messenger but she won't need to if she uses the desktop site to view messages. Then she can set her Facebook notifications to go to her gmail account, then in gmail app she needs to make sure it is set to receive notifications for gmail, then when she gets messages or activity on Facebook she will get a gmail notification in her status bar letting her know to check Facebook, then she can open the bookmark to view it. That is just as convenient as having the two apps but without all the strain on the device, also takes less space on internal and has less junk running in the background eating mobile data and draining battery.
As for her texting apps such as WhatsApp, Kik, Snapchat, etc., she needs to pick 1 or at the most 2 of them and leave the others alone, her device will run much faster and smoother.
You can try booting to recovery and wipe cache partition(not factory reset).
As for fastboot and SP flashtool not working, do you have USB debugging enabled in developer options on the device?
well thanks for your reply your advice about phone usage is great but wouldn't matter If I can't revive this phone anyway yes I tried both to wipe cache partition and wipe data and yes I enabled USB debugging but in case of SP flash tool all i need to do is have the proper drivers shutdown the phone click download in SP then connect the phone using USB cable then the red bar would fill up then another yellow one then a big green OK tick and nothing would change in the phone and for Fastboot all I need to do is shutdown then power + volume up then select fastboot then connect the phone then open cmd and type fastboot devices it would show the device Id then use the command fastboot flash recovery recovery-cwm-y520.img then I get the error "FAILED (remote: partition 'recovery' not support flash)" interestingly I got my hands on a normally working similar set which I tried several things on it like *#*#7378423#*#* It accepted the code but didn't do/show me anything just like my broken set then having the set in Fasboot mode I tried "fastboot oem device-info" which yielded nothing but ... just like my broken set other things I tried on my broken set I tried following this guide http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 using "Mtk_Droid_Tool_v2.5.3" to create CWM recovery for my phone and got the error
error :no find kernelgz
error: no split boot image
then I tried to use easy magic Philz touch installer which eventually asked for root access on the phone
but I can't since I tried every root method and didn't work.
I even made a logcat if it would help I could attach it
mostafa_0017 said:
well thanks for your reply your advice about phone usage is great but wouldn't matter If I can't revive this phone anyway yes I enabled USB debugging but in case of SP flash tool all i need to do is have the proper drivers shutdown the phone click download in SP then connect the phone using USB cable then the red bar would fill up then another yellow one then a big green OK tick and nothing would change in the phone and for Fastboot all I need to do is shutdown then power + volume up then select fastboot then connect the phone then open cmd and type fastboot devices it would show the device Id then use the command fastboot flash recovery recovery-cwm-y520.img then I get the error "FAILED (remote: partition 'recovery' not support flash)" interestingly I got my hands on a normally working similar set which I tried several things on it like *#*#7378423#*#* It accepted the code but didn't do/show me anything just like my broken set then having the set in Fasboot mode I tried "fastboot oem device-info" which yielded nothing but ... just like my broken set other things I tried on my broken set I tried following this guide http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5 using "Mtk_Droid_Tool_v2.5.3" to create CWM recovery for my phone and got the error
error :no find kernelgz
error: no split boot image
then I tried to use easy magic Philz touch installer which eventually asked for root access on the phone
but I can't since I tried every root method and didn't work.
I even made a logcat if it would help I could attach it
Click to expand...
Click to collapse
The advice does more than help, its actually the REAL solution to the problem. If you get it fixed and she's still using all that crap it'll just cause issues again, I'm sure you don't want to have to go through all of this a second time, right?
Droidriven said:
The advice does more than help, its actually the REAL solution to the problem. If you get it fixed and she's still using all that crap it'll just cause issues again, I'm sure you don't want to have to go through all of this a second time, right?
Click to expand...
Click to collapse
God no of course not I will till her to keep her apps in check and use as minimum social apps as possible but right now that won't help me revive this phone :crying:
mostafa_0017 said:
God no of course not I will till here to keep here apps in check and use as minimum social apps as possible but right now that won't help me revive this phone :crying:
Click to expand...
Click to collapse
I don't get how installing a game caused this, I believe there has to be more to the story somewhere, somehow.
Besides, with some of the steps you've taken, you've probably created other issues than it started with. Whatever you do, don't format the device in SP flashtool, you'll probably lose IMEI if you do that.
Droidriven said:
I don't get how installing a game caused this, I believe there has to be more to the story somewhere, somehow.
Click to expand...
Click to collapse
me too man me too I didn't believe it at all installing an app won't do all of this but at one point when I was rebooting I got this suspicious message which I took a couple of bad quality pictures for it here http://imgur.com/a/RIGqD
actually I have grown very confident dealing with the phone that no matter what I do It wouldn't matter since it will come back just as always and now I didn't create any other issues since no matter what I hit a dead end the device revert back no matter what I do, Do you feel me I am starting to go insane I am pretty sure even If I tried to brick this device on purpose I won't be able to.
mostafa_0017 said:
me too man me too I didn't believe it at all installing an app won't do all of this but at one point when I was rebooting I got this suspicious message which I took a couple of bad quality pictures for it here http://imgur.com/a/RIGqD
Click to expand...
Click to collapse
Your pic keeps directing me to the imgur app to view it, I'm not installing the app just to view it, why not just upload the pic as an attachment to your post and it will display in your post instead.
Sorry old habits die hard I used to talk in this one forum before and their rules forbid to upload images or anything actually as attachments except in extreme cases here they are
hmmmm strange can't find the attachment button guess I will just post direct links hope they work
http://i.imgur.com/OrSWbzE.jpg
http://i.imgur.com/EcmrDlI.jpg
mostafa_0017 said:
Sorry old habits die hard I used to talk in this one forum before and their rules forbid to upload images or anything actually as attachments except in extreme cases here they are
hmmmm strange can't find the attachment button guess I will just post direct links hope they work
http://i.imgur.com/OrSWbzE.jpg
http://i.imgur.com/EcmrDlI.jpg
Click to expand...
Click to collapse
When did you say it displayed that? That looks fishy, the grammar is a little off as if whoever made that didn't quite know the language, kinda like the way grammar isn't quite right like some of the questionable Chinese apps known to be malware.
If you're using a browser you have to select "go advanced" under the box you reply in, then you'll see "manage attachments"
If you're using an app you should see a paperclip symbol or a pic thumbnail.
Droidriven said:
When did you say it displayed that? That looks fishy, the grammar is a little off as if whoever made that didn't quite know the language, kinda like the way grammar isn't quite right like some of the questionable Chinese apps known to be malware.
If you're using a browser you have to select "go advanced" under the box you reply in, then you'll see "manage attachments"
If you're using an app you should see a paperclip symbol or a pic thumbnail.
Click to expand...
Click to collapse
Yeah thanks found it and it displayed this only one time when I was rebooting after doing various things and I never saw it again and yeah the grammar felt really strange when I googled its content I only found a couple of Spanish forums talking about this but couldn't get any information about the source of this message and that's why I thought about the logcat in the first place.
the same problem
hi i have the same probleme with my huawei y520 u22 i can do nothing just start up the phone i got the message and i can do nothing when i try to unistall any app the phone restart and go back to the same situation wipe cache and wipe data nothing change flashing 1000000000000000000 roms nothing change any one can tell me there the problem is
as i think the flash memory is the problem its blocked in write and read.
any solution plz
I read this and just think, what the hell... i can not understand why "/data" is write protected. Just some thoughts running through my head:
- phone is not rooted and completely stock, but factory reset not working!? in this case ask for warranty and send it back to seller!
- if no warranty, ask Huawei for support. don't tell much, just claim factory reset is not working.
- ask any mobile repair shop, they have special hardware like Octoplus Box and can do factory reset.
- if possible - make a "backup user data" with Android system recovery, you may restore it on working phone, later.
- if you have read-access to "/cache/recovery" look for file "last_log" and copy to sdcard. "/proc/emmc" and "/proc/partitions" are another useful files. keep this in case you have to manually create the scatter file.
- you can use MediaTek SP Flash Tool Readback function in download mode to make a ROM backup dump. for readback you need to install VCOM Drivers, then first click Read back, then connect the phone to PC while switched off and insert battery. MTK Droid Tools will then help to segment the partitions from it. or readback every partition separately with scatter file. the most important files are "nvram.bin", "preloader.bin", "boot.img", "recovery.img".
- if phone is locked, ask Huawei for unlock code (not sure if this works on broken phone). there are different kinds of S-ON some will lock only bootloader, some lock all partitions, too.
http://www.modaco.com/forums/topic/362724-official-code-request-to-unlock-the-bootloader-final-post
- try fastboot mode factory reset (not sure if working, just googled this stuff i found).
http://www.hardresetandroid.com/hard-reset/huawei-hr/huawei-ascend-y520-hard-reset-code-format-solution
- once you have unlocked the phone, do factory reset. phone should boot now. its hardly imaginable that "/system" is damaged because of never rooted the phone.
- if still not working, you should now be able to flash custom recovery, too. be careful, select tested binary for your special phone model only! flash in fastboot mode. avoid flashing with SP Flash Tool as long as you not absolute sure that scatter file is 100% correct (MTK Droid Tools may give you wrong scatter files for devices > 4 GB!)
- from custom recovery, you should able to root the phone via adb root method or install the "supersu.zip"
- once you have root, you can mount data partition read-write from adb shell (in recovery mode) and format or delete it. of course the custom recovery has a wipe data option, too.
- installing aroma file manager zip is another way to browse and modify everything in recovery mode. you can copy files from similar phone into "/system" folder, if phone still not working properly.
- don't restore a full backup from similar phone (especially NVRAM folder), this may clone IMEIs and WiFi MAC address.
- you can install a stock rom zip from custom recovery instead, and use my script bckp2cwm.zip to convert the user data backup into cwm format and restore "/data" folder only (converting script requires linux pc).
- delete suspicious apps from "/data/app" + "/data/dalvik-cache" + "/data/data" (every app has three entries with similar name). do it in recovery mode with aroma file manager, or on linux pc from backup file during converting (at this point where script is waiting for user input).
- search and read for "unbrick guides" on forum.xda-developers.com, as long as it is not a physical damage (Vol keys not working, emmc wearing out, etc) there must be a solution to get this phone working
- if no warranty, ask Huawei for support. don't tell much, just claim factory reset is not working.
yeaah I don't think they would respond with any helpful answer and would probably tell me to send my phone to the nearest service center.
- ask any mobile repair shop, they have special hardware like Octoplus Box and can do factory reset.
That's what I settled for eventually and I already sent it to my sister and told her to visit any mobile repair shop that has boxes like miracle box and such.
- you can use MediaTek SP Flash Tool Readback function in download mode to make a ROM backup dump. for readback you need to install VCOM Drivers, then first click Read back, then connect the phone to PC while switched off and insert battery. MTK Droid Tools will then help to segment the partitions from it. or readback every partition separately with scatter file. the most important files are "nvram.bin", "preloader.bin", "boot.img", "recovery.img".
done that already but what I got in the end didn't help me to fix the phone note that I don't care about the phone's content sure I care about the IMEI but the phone is not affected by any write attempts so I am not so worried.
- if phone is locked, ask Huawei for unlock code (not sure if this works on broken phone). there are different kinds of S-ON some will lock only bootloader, some lock all partitions, too.
I searched online and in threads talking about custom roms and recoveries for this phone and not a single one of them mentioned anything about the bootloader being locked.
- try fastboot mode factory reset (not sure if working, just googled this stuff i found).
haven't tried that but will try it ASAP since I don't have the phone right now.
One last note the phone boots normally but as I described in my later posts I can't edit anything without it reverting back after restart like changing the wallpaper or uninstalling an app.
And anyway thank you for your respond.
did you try to get (temporary) root access?
aIecxs said:
did you try to get (temporary) root access?
Click to expand...
Click to collapse
Not sure of What you mean but I think I tried and failed you can tell me What you mean exactly and I will tell you If I tried .
Edit: Alright I googled it and turn out to be temporary root for locked bootloader devices no special procedure just the same procedure as in permanent root but will lose root as soon I reboot again I tried a lot of rooting methods including kingoroot and 360root.
Not sure, too.. installing kingoroot.apk and root the phone may give root access until reboot (can't remember if rooting requires a reboot)?
Brainstorming. Lets come from other side. When you intend to write a malware - how would you realize this setting?
one thing is remount /data partition read-only, but is this really enough? what happen if /data is not writeable anymore - apps should crash or give errors on write cycle, didnt they?
but you claim phone is changeable until reboot. so we need the possibility to let them write in some other memory without noting that it storage has changed.
another way is copying /data to any hidden storage, and restore it on each reboot, but this should be time consuming, didnt it? and where can this amount of data be stored? sdcard? cache partition?
besides this, guess the malware needs root access to modify /data. or is it imagineable to change it without root access? lets find a conception to understand whats going on
No reboot is fast and not time consuming and I am always working on the phone without the SD card and about apps sometimes uninstallation is complete and the app disappear to show again after reboot and sometimes the phone restart upon uninstallation of an app