Related
Hello everybody !
I'm new to this forum, so I don't know if it's really the right place to post this. If it ain't, then please excuse me.
I recently moved to China and acquired there a Samsung Galaxy Y S5368 (Android 2.3.6), which seems to be a local version of the S5360 (that you may know better).
It was part of an offer proposed by of the biggest telecom company, and the delivered version is very limited... I thus want to root it, but it has been impossible for now...
I tried to root it through superoneclick, as it seems to be recommended by all the chinese websites talking about this matter. I installed the samsung drivers with success, enabled USB debugging, unmounted the SD card (in fact put it out from the cellphone), used the last superoneclick version 2.3.3 (which for others seems to be ok), but when i try to root the log always end up this way :
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[-] Error creating Nydus: Permission denied
END:31184
I saw on the web other people having the same problem, but no answer yet...
Does anyone know what could be the problem, and how to deal with it ? Is there a clear tutorial on how to root a S5368 (Android v2.3.6) / S5360 via superoneclick ?
Thanks in advance.
Pierre
Tutorial
Essential Pre Requisites:
All the data present in your device should be backed up so that just in case if any data gets corrupted or erased, the same can be easily restored with the help of simple steps mentioned below. Don’t make use of KIES PC Suite to back up the data as with the below mentioned steps you can effectively backup the data.
SMS – Use “SMS Backup & Restore app”,
Contacts – Sync with the Gmail application,
Call Log - Call Log and Restore
Songs, Videos, Files – Copy to internal / External SD Card,
APN and MMS Settings – Note down from the path “Applications > Settings > Wireless and Network > Mobile Networks > Access Point Names”
Minimum battery left in the device should be 60% so as to avoid device from getting turned Off in the middle of firmware update. Also, you need to ensure that all the antivirus suites in your phone and PC are completely disabled.
So assuming that you have followed all the instructions mentioned above, it’s now time for you to get started with the tutorial to Root Samsung Galaxy Y.
Procedure to Root Samsung Galaxy Y Pro Duos:
Download the Galaxy Y Pro Duos Rooting Package from here to your computer and once you do so, connect your phone to the computer with the original USB cable. Place the file in your SD Card and not in any of the sub folders.
After copying the file, remove the connected USB cable and enable the USB debugging in your Galaxy Y Pro Duos phone from the path “Settings > Applications > Development > USB debugging”. The USB Debugging option should be ticked.
Now turn off the device so that the phone can be then entered in the recovery mode. The recovery mode can be entered by Pressing and holding the Home button and then the Power button. If the device gets turned ON in the normal mode then you need to again try the same process of getting into the recovery mode.
Now, in the recovery mode select “install zip from sd card” > “choose zip from sd card” > and select the “Rooting Package”. Once the zip file is updated successfully, you now need to select “++++ Go Back ++++”.
Now, you need to select Wipe data/factory reset and also you need to select Wipe Cache partition and then reboot your device by selecting reboot system now with the help of Volume rocker keys.
Once you are done with the cache clearing and wiping the data, you now need to select “reboot system now” option for restarting the device. Once the device is restarted, you then need to Download & Install the Superuser application from the Google PLAY Store.
Note: Just in an unfortunate event just in case if you face any issues in the middle of firmware update, you need to again follow the instructions from the start. If the device gets into the boot loop mode then you will have to re insert the battery and re apply the firmware update again.
So congratulations, you have now successfully rooted the device. Do let us know in the comments section just in case if you face any issues as we will try our level best to sort out the same.
^^ full tutorial. simple google search
tutorial for rooting samsung galaxy y
^^^ type that, first link on type.
First, I thank you much for your quick answer and all the explanations given.
I forgot to mention I did search a lot on google before coming here requiring your help, saw the site and read the tuto you're talking about.
Unfortunately, the phone is well locked and it's impossible to access the recovery mode by pressing the HOME + Power buttons (nor via any other combinations that I found here and there, like HOME + Vol UP + Power buttons).
In fact, I first spent a lot of time trying to access this recovery mode, as I've already copied an appropriate zip file into the phone in order to root it, but without any success......
Then I heard about superoneclick on chinese forums, and thought it could save me, but once more it's not that simple.
I still need help, whether to know :
1. how to access recovery mode when buttons combination doesn't work and phone still not rooted ;
2. or how to use superoneclick properly and get rid of this "Error creating Nydus: Permission denied".
Thanks much in advance, cause I really don't know what more I could do now.
Does anyone know how I could do ?
Make sure your connection is internet mode.
Sent from my VS910 4G using XDA
Yeah internet mode has been activated, and it doesn't fix the problem...
Thus I decided to try again the method which have been posted above, via the recovery mode.
As explained above, I can't access the recovery mode via the 3 buttons combo.
I found the famous thread where the heimdall method is documented and wanted to try it, but I can't get the proper files since multiupload.com seems to be down.
Moreover, I can't find the files via google and can't post in the related topic (since vgot less than 10 posts...).
Could someone help me to find the following files in order i try to apply the 3BR procedure ? :
adbDownload.zip
RAZ_P-SBL_SGS.tar
Thanks much in advance.
Pierre
picard13 said:
Could someone help me to find the following files in order i try to apply the 3BR procedure ? :
adbDownload.zip
RAZ_P-SBL_SGS.tar
Click to expand...
Click to collapse
Ditto. I found (Here) a file called PSbl_stockJPU.tar that appears to contain some bootloaders, but I can't tell if they are any good.
So, anyone have the above mentioned files?
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
How to get the most complete backup, which is possible with locked bootloader and no #Root?
Hello everybody.
This step-by-step Guide will show you, how to get the most complete backup from a Nexus device,if your bootloader is not unlocked.
Once, i also had some problems and confusion with this backup, but finally i understood. So i'm posting this thread for some other users, which are maybe confused.
First of all, great thanks to @WugFresh for the Nexus Root toolkit, and for the early help.
This can be helpful, if you want to unlock your bootloader, but you still need to back up some important data.
With unlocked bootloader, it's quite easy to take a backup, which doesn't exclude anything. That's the Nandroid w/ Backup.
But with locked bootloader, it's a little bit (much) harder, because the nAndroid/W Backup will not be useful at all.
The problem is, that unlocking bootloader will wipe out all user data/apps/etc., which is present on the device. Locking it again will do the same. There's no way to avoid the wipe, which will make all data unrecoverable, but you can back up as much data as possible.
I recommend to unlock the bootloader, straight away after you buy any nexus device, before saving any data to it, to avoid those restrictions. It's truly worthed it.
The Factory Images of all Nexus Devices can be downloaded from this nice place here, if you want to change your Android Version manually: https://developers.google.com/android/nexus/images?hl=de
Google excludes all 4.4.1 or 4.2.1-Versions on the website, but other version history is included, and the download speed is very fast there.
This is, what the backup will include:
> Full User Data Storage (Without NRT)
> All APK's of Free Apps
> All Data of Free Apps
> Full Data of Paid Apps
> AndroidManifests.XML of Free/Paid/System apps
> SMS
>Call Logs
>Contacts
This is, what the backup will exclude:
APK's of Paid Apps
Data of System Apps
APK's of System Apps
Network Configuration
WiFi-Passwords and SSiD's
A Nandroid w/ Backup does actually include everything, which is on the device, nothing (except. deleted recoverable data) is excluded.
Part 1 (Without NRT) - User Data Storage
For this part, you should do following:
Make sure, your computer supports MTP. Connect your device to your Computer's USB Port.
1. Reboot your device (better to safe mode) - If your computer detects the device, jump to step 4.
2. After Reboot, drop the drop-down-menu by swiping down from the upper screen.
2.1 Go to the USB-Connection-Notification and tap it.
3. If MTP-Connection is not enable, enable it
4. You're now viewing the Internal Storage of the Drive with the File Explorer of Windows.
4.1 Now press STRG+A.
4.2 Now copy or move the data to your desired destiantion (On Android 4.4.2, never move the data from the device, because that can Trigger a full data loss of the internal user storage, due to a software bug. Better →copy→delete.)
4.3 If you've got many files, and the Progress Bar is stuck at zero, wait around up to thirty minutes and see what happened. In those thirty minutes, Windows counts the files and calculates the - this is needed for MTP. Too Bad ;(
4.3.1 If something happened in those thirty minutes, (progress bar) simply wait until the end.
4.3.2 If nothing happened, try not to copy/move all file at once.
5. Make sure, that every desired file is in the output folder. (4.4.2 Software bug might exclude newer files.)
6. Go to [Part 2], to backup the apps with their data.
Part 2 with NRT - Apps, Application Data, AndroidManifest etc.
You have to connect your device to the computer with a MicroUSB-Cable. The length of the cable is not important, but please make sure, that it's attached properly.
Installing the program is possible, without your nexus device itself, but you'll need it.
[Part 2.0 - Preparation and Installation of NRT]
First [i forgot, what i wanted to write here. Will be added by edit, please excuse me ]
You can download the lastest version of NRT right here (Currently, it's 2.0.5, while this text was written)
It's an offline (standalone) installer, so that the Installer does not require any Internet connection to install NRT, if the download of the installer finished. It will not download additional files and it's also free of adware.
Optionally, you can set the installation directory manually.
[Part 2.1 - After Installation]
After finishing the Installation, you will have to open the toolkit. Possibly it will ask you, which device model + Android Version you have got. Auto-Detection only works, if your device is attached to the computer properly.
Probably, a message will show up, which wants you to download the following three things:
→Modified Boot.img
→TWRP (Team win Recovery Project) Recovery
→@ChainFire SuperSU (Currently v2.4.6)
So you have to click on „Download + Update all file dependencies"
After the NRT has downloaded a few files, it will automaticly go to the GUI's Main Page with it's LiveLog.
[Part 2.1.1 - Google Driver Installation]
For this Step, you have to click the big button in the main GUI Page, in the area "Initial Setup", in the upper right corner.
As far, as i know myself, it's recommended to install the Google Drivers. The name "universal drivers" sounds attractive, but i did not test, whether it works, but i think, it does also work fine. But there's also a big number for „Recommended Solution". In my case, the tool recommended me [#1].
[2.2 - GUi]
Now, it will ask you, to enable the USB-Debugging. NRT will tell you, how to do it:
1. Go to the Settings Menu.
1.1 Go to the System Information
1.2 Tap the Build Number (e.g. KOT49H for Android 4.4.2) seven times, to enable the developer options. You can also tap it more than seven times, but this will not have any effect.
2. Open the Developer-Settings.
3. Enable „USB-Debugging"
3.1 If needed, you can confirm to allow your computer. The RSA-Fingerprint of your computer will be displayed.
3.2 For sure, also go to the USB-Connection settings (through the Drop-Down menu or the setting menu), and uncheck MTP or PTP or whatever (everything, which is present.)
You're now on the Main Page of the GUI.
On the left, there's an Area, which is called: „Backup + Restore“.
There are two buttons labeled [Backup] and [Restore].
[Restore] is for restoration purposes, so click on [Backup].
[2.3 - App Backup]
On the area „Backup all Apps", you see 2 tickboxes.
Please do not tick the first one, because the first one would require an unlocked bootloader. If you do, the program would fail
[ ] System apps+data
[✓] Shared Data
After that, just go and click on [Create Android Backup File], which will create an *.ab File. (not *.adb) Later, you can restore the data from the AB file, whenever you want.
After you clicked this button, a window with some relevant information will show up. Please take your time and read it. It can be pretty useful.
Please don't forget to turn Airplane Mode on. I personally recommend being in Safe Mode. (The computer can run normally, but the device should be in fresh safe mode without opening any app.)
After you click on [OK], the program will ask you, where you want to save the .ab-file, and what the filename should be.
The Standard is „MM-DD-YYYY_HH-MM.ab" - I personally use YYYYMMDDHHMMSS, the Timestamp, which is known from the Wayback Machine.
After that, the Toolkit will try to reboot your device. But then it will not boot into safe mode. So please click [save] at the moment, when the device is already rebooting into safe mode.
Make sure, that your Computer's RSA-Key(Fingerprint) is automaticly accepted by the debug mode. The Toolkit will only wait five minutes for the device. If the waiting time has expired without success, an error message will show up. It says: „Notification: Waiting for device operation timed out. [...]"
If your device can't be detected, read the information in the timeout-window. It's worth reading it and will maybe solve your problem.
If your device is detected properly, your device should disply a confirmation message all over the screen. Try confirming fast, otherways NRT will timeout.
But if you want, you can lock it with a password, which you'll need, if you want to read/restore from the backup anytime later on. Please take care about case-sensitivity and to avoid additional problems, it's not recommended to use those emoticons on the KitKat-Keyboard.
Now, the backup starts.
While NRT is indicating, that the backup is running, the device will display, which package is being backed up. Now, please wait, until it's finished.
[2.3.6 - Finish]
The output file is now compressed, so a smaller file size than uncompressed is expected.
There are tools, where you can read those ADB-Files.
Make sure, that the filesize is reliable. If the backup is blank (Zero Bytes) or just a few kilobytes, something went wrong. Retry the backup, if this is the case.
[2.4 - Other things]
Now, you have to do the same with following things, if possible or needed:
> SMS
> Call Logs
> Contacts
> Network Configuration (Root needed on Android KitKat/Higher)
Just give it a try.
Part 3 - VirtualSD-Backup
This is non-urgent, so if it does not work, it's no problem.
You have to go to the Backup Menu again.
This is very similar to Part 1, and easier, but does only work up to Android 4.3(.1).
If you want to do this on 4.4/Higher, you will need an unlocked bootloader. Vicious cycle.
----
@WugFresh, @anybody else; if there's anything i missed, or i described wrong here, like false information, please let me know it by sending me Private Message or better Post in this thread.
If there are problems, feel free posting here No problem is irrelevant here.
I hope, my guide was able to help some people here.
I wish you to have very much fun with NRT‼
Test Device: Nexus 7 2012 - 32 GB IntMem - WiFi - Not mobile - Android 4.4.2 KOT49H
Ask Questions
Please feel free asking questions here. :laugh:
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
I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.
hardya said:
I have oneplus one came from chineese retailer already rooted and with adware. always meant to reflash with straight CM or with a version of AOSP, but ended up use adb (which I have for development, though I am NOT experienced in using adb, flashing rom or what ever only programming) to disable a number of apps and it seemed to be stable.
More recently I had a phone crash following the crash of an app that I think is the CM app launcher, something begining with t, trebuchet?, i dont recall. Since then the phone keeps rebooting and I cannot seems to use adb, the device is either not present or offline.
I can boot to cyanogen recovery which offers:
- reboot system now
- apply update
- apply from adb
- choose from internal storage
- wipe data/factory reset
- wipe cache partition
- wipe media
If I select apply from adb then the device is nolonger offline but in sideline mode, but I don't think this is what I want.
I never liked CM and I had always thought that I might try to flash with a version of AOSP if possible and I wondered if now was the time. I thought TWRP might be useful for this and the first step to installing this was:
C:\...\Downloads>adb reboot bootloader
but I get
error: closed
I briefly see the debugging notification before the phone reboots but in adb it is always not present or offline.
How do I get to the point of either solving my repeating reboot at least or preferably installing a version of AOSP that would be compatible with OnePlus One, preferably without destrying data. I think the data is in a different partition or something but I have forgotten the little I learnt about this a few years ago.
I would be so grateful of some help and learning, right now to all intents and purposes I have a nice looking brick.
Click to expand...
Click to collapse
Did you try factory reset?
Thank you so much for your the suggestion, I appreciate it.
Not yet I haven't. I'm not familiar with the CM Recovery Software and the option is entitled "wipe data/factory reset". Do you happen to know if this means bother or either and if selecting this explains more and gives options before proceeding. Key is I want to avoid wiping data if possible because while most is sync'd offline some is recent and not or not for particular reasons.
If there's a choice then will "factory reset" leave personal data alone? Do you know, will the factory reset likely be to version/adaptation of CM put on by rooting retailer PLUS anoying/mal/ad/ware apps put on by rooting retailer.
If this is my only option then I will go ahead and do it and take the hit.
If following this, it is possible to install a stable Android 7.n.n AOSP only that will support the hardware and leave data intact (ONLY LEAVE DATA IF POSSIBLE) I would be very grateful for a clear and complete script to achieve this. I was a professional developer for 20 years, now semi-retired, so I know what I know and what I don't know in terms of foundational knowledge, taking care etc etc, but I am very inexperienced in flashing phones and using ADB except the fact the eclipse/android studio uses it.
I used a windows script to install fastboot if that is any help (though the script did show some errors it still said "All Done!" at the end. Tried to C&P the errors but failed). I can also try to install TWRP (or what ever) if that's any help.
Many thanks would really appreciate your help in my getting my OnePlus One working and stable again.
Andrew.
hardya said:
Thank you so much for your the suggestion, I appreciate it.
Not yet I haven't. I'm not familiar with the CM Recovery Software and the option is entitled "wipe data/factory reset". Do you happen to know if this means bother or either and if selecting this explains more and gives options before proceeding. Key is I want to avoid wiping data if possible because while most is sync'd offline some is recent and not or not for particular reasons.
If there's a choice then will "factory reset" leave personal data alone? Do you know, will the factory reset likely be to version/adaptation of CM put on by rooting retailer PLUS anoying/mal/ad/ware apps put on by rooting retailer.
If this is my only option then I will go ahead and do it and take the hit.
If following this, it is possible to install a stable Android 7.n.n AOSP only that will support the hardware and leave data intact (ONLY LEAVE DATA IF POSSIBLE) I would be very grateful for a clear and complete script to achieve this. I was a professional developer for 20 years, now semi-retired, so I know what I know and what I don't know in terms of foundational knowledge, taking care etc etc, but I am very inexperienced in flashing phones and using ADB except the fact the eclipse/android studio uses it.
I used a windows script to install fastboot if that is any help (though the script did show some errors it still said "All Done!" at the end. Tried to C&P the errors but failed). I can also try to install TWRP (or what ever) if that's any help.
Many thanks would really appreciate your help in my getting my OnePlus One working and stable again.
Andrew.
Click to expand...
Click to collapse
Okay,since you want to flash Aosp N,leave that factory reset thing.
https://forum.xda-developers.com/showthread.php?t=2788632
This thread should be enough atm.Everything has been explained,and it's just simple copy paste,so,even if you're unfamiliar with adb,you should be able to do just fine.
Just follow,install adb/fastboot drivers,unlock bootloader,and flash twrp.
Now,unlocking bootloader will format internal storage,which means everything....but,a simple adb command should be able to back everything up into your pc.
Ensure your adb/fastboot drivers are already installed,and using adb devices in cmd shows your connected device id,before below process!
adb backup -apk -shared -all -f C:\Users\NAME\backup.ab
Where "NAME" is the name of your Windows user name.
On the device, a new screen should appear. If you want to encrypt the backup, enter a password -- otherwise, tap Back up my data. The backup will begin, and you'll find the backup file in the folder declared in the backup command.
Depending on how much data your device holds, this process can take quite some time.
The restoration process is simple. Connect the device to be restored and (from the same location you issued the backup command) enter the command:
adb restore C:\Users\NAME\backup.ab
Where NAME is the name of the same Windows user from the backup process.
Again, depending on how much data is on the backup, the restore process can take some time.
Click to expand...
Click to collapse
When you're done doing all of this,just follow any rom's thread instructions to flash that rom.
Btw,you're on Cos13.1.x,yes?
So sorry for not replying to say thank you sooner, I have been busy with family issues.
Thank you so much for your response, I really appreciate it. I shall take a look at this soon and try to get regular android N on the phone soon. Thank you.
I'm just starting to read and work through this. Just to clarify, re my original post, is the fact that my phone is continually rebooting and that adb shows the device as offline a problem? Will I still be able to use adb to backup the phone contents? Do I need any special understanding to do that?
I finally came back to this and flashed a new rom carbon rom. I only noticed afterwards that there is very little support for this rom and I've had some issues.
If you think the issues are in some way generic and you have come accross them before you may have some ideas:
- there is no built in task manager and third party ones do not seem to cover the apps I am interested in. Any ideas why there is no built in task manager anymore like there used to be and how one might be able to turn it back on?
- the camera does not work and the open camera I installed instead has some image faults (or misunderstood feature). Big line down the middle of the image.
Any ideas.