[Q] Phone bricked? :( - Optimus One, P500, V General

Hello guys,
today i tried to flash back thunderg recovery, so i downloaded the 2.2.1 .img version and zipped it, then i followed the following procedure
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
# reboot recovery
Click to expand...
Click to collapse
now when i boot i get a blank screen with the following message:
fastbod mode started
udc_start()
-- suspend --
-- reset --
-- portchange --
-- reset --
-- portchange --
Do you guys know if there is a chance to fix this or i have to send it to lg support?
EDIT: I just remembered about a program called KDZ, I will try to download the latest .kdz update and flash it through windows, if the program will recognize my phone ofc.. (hopefully)..

use kdz and reflash your phone with an original rom and u'll be ok
hapened to me too
and thake care
# flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
this one is not ok for recovery 2.2.1 that u are using

# flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
i obviously changed this line with the name of my .zip, it was like the same, just with 2.2.1 instead of 1.1.0 :/

ok but u have to use the name of the .img inside the zip
and why don't u use the original zips like thunderg 1.1
and afther that upgrade thunderg to 2.2.1

phone was not found...
well, i see an "android" device not installed on the pc, i'll try this at home cos i can't install sdk at work.. hope it will work there

but u got him working?
wave u used kdz to reflash original rom?

It did not work now, as KDZ Updater could not find my phone..
I guess this is a problem with the drivers and the SDK, at least I HOPE SO.. as i don't have SDK installed on this pc but only LG suite.
So i'll try to repeat the procedure once I'll be @ home on my desktop

enriquez90 said:
It did not work now, as KDZ Updater could not find my phone..
I guess this is a problem with the drivers and the SDK, at least I HOPE SO.. as i don't have SDK installed on this pc but only LG suite.
So i'll try to repeat the procedure once I'll be @ home on my desktop
Click to expand...
Click to collapse
Yes, probably it is problem of driver. You need to have drivers installed. Also sometime is "shaking" and some other stupid task to get it working. I know, it sounds like joke, but I have this "steps" confirmed more than once.
http://forum.xda-developers.com/showthread.php?t=883314

the_error said:
yes, probably it is problem of driver. You need to have drivers installed. Also sometime is "shaking" and some other stupid task to get it working. I know, it sounds like joke, but i have this "steps" confirmed more than once.
http://forum.xda-developers.com/showthread.php?t=883314
Click to expand...
Click to collapse
truely this guide was my saviour too when i bricked my phone just follow the instruction mention by error carefully

ok I managed to install 2.2.2 lg update through the emergency mode, so my phone is now operating at its full potential .. oh well, not yet, i'll have to flash a rom again
thank you guys

Good problem solving skills!
But I don't understand why so many people don't just flash the files from recovery.
Sent from my LG-P500 using Tapatalk

lekhwani said:
Good problem solving skills!
But I don't understand why so many people don't just flash the files from recovery.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
Coz they don't have recovery on phone and don't know install it, so they choose an easy way.
Sent from my LG-P500 using XDA Premium App

Related

Verification failed while applying G2 OTA update

Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Completely the same problem with HTC Hero after European OTA update. It has been rooted while ago (by following instructions from this forum) and now after setting up date in the future and confirming update, phone reboot and I get "Android System recovery" screen with menu and this message bellow it:
Build: CyaanogenMod v1.4 + JF
Finding update package ...
Opening update package ...
Veryfing update package ...
E: No signature (218 files)
E: Verification failed
Installation aborted.
Click to expand...
Click to collapse
I have the same problem (I did not write down the message, so I'm not sure which "Build:" was listed) .
The update fails, the phone reboots and then works under the old build. Under "settings/about phone" there is also no info about the update. Can one force the phone to download the update a second time? Would this help?
Bye
Nick
P.S. I'm running the phone in Germany over e-plus as network provider. The updates was done over a WiFi connection. The phone is not branded - was from the free market and not from a provider.
Hey,
got the same problem. At least I could extract the official OTA-update-zip to publish it here (see attachment)
There also is a "recovery.img" in the update zip, so I guess usually the OTA update will kill custom recovery bootloaders. We could replace the "recovery.img" in the zip with a hacked one before applying the update.
However first we should fix the verification error...
P.S.: Also Germany, not branded, Vodafone Network
Does anyone know if I will lose all my data if I reflash the original recovery.img onto my phone?
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Flashing the original recovery.img should not be a problem.
However, I don't want to lose root access, and thus I will wait for the official HTC 2.1-update (hoping someone publishes it online) and then flash it by myself..
I don't mind losing root access at this moment (the reason I rooted my phone was to get wifi tethering but never got it working with a mac).
Since I am total noob with android stuff, I would highly appreciate some step by step instructions or link where I can find what to do. Thanks guys.
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
rseffner said:
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Click to expand...
Click to collapse
What was the rom you were using when you flashed the official recovery?
alvaritolalala said:
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
Click to expand...
Click to collapse
Try the following:
- Copy the recovery.img to your SD card
- Turn off the phone, turn it on with Buttons "HOME"+"ONOFF" pressed such that the ra-recovery which you already have starts
- connect to your phone by cable using "adb shell"
- Then with root access you can flash the image by typing "flash_image recovery /sdcard/recovery.img"
This should do it
jamesots said:
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Click to expand...
Click to collapse
hey,
I had same problem
go to All programs--> Recovery Flasher--> Restore backup
then restart and update OTA
Greetings from Zagreb, Croatia
Hey guys.
So, for those of you, who do NOT care about root for now, here's what worked for me:
1.: Download the zip-file with the OTA Update, mentioned on the first page and extract it.
2.: Connect your Hero to your PC and copy the recovery.img from the OTA onto your sdcard. Disconnect from computer.
3.: Boot your phone into the bootloader (Home + PWR).
EDIT: Now connect the phone to the pc again!
4.: open the command prompt of your pc, navigate to your Android SDK folder. (If it is not installed, download it and make sure you've got the needed drivers. Otherwise: Download them, using the Setup.exe from Android SDK)
5.: Here are the needed commands:
Code:
adb shell
$su
mount -a
flash_image recovery /sdcard/recovery.img
6.: reboot your phone after exitting the command prompt.
7.: Factory reset, reboot again
8.: And well, wait for the update-window again and be happy, now it should work
EDIT 2:
Any questions? Just leave a reply
@Revoluzifer
OK I did exactly as you explained, but having problem with su command:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
I know I know, you're going to say my phone is not rooted at all But believe me it was and some apps that require root access are there (screenshot, wifi tether etc.).
I even tried to find su cmd with find:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
But got nothing as you can see.
Ideas?
@dinke:
Which bootloader / recovery console is installed?
Means, what do you see, after booting with Home + PWR?
Also try to input $su instead of just su.
But first tell me your "hack" if any
@Revoluzifer
Thanks for quick reply
I see Android system recovery screen, not sure if this is nandroid or what but have this text on the screen with following options:
Android system recovery <2>
Use trackball to highlight;
click to select.
[Home+Back] reboot system now
[Alt+S] apply sdcard:update.zip
[Alt+W] wipe data/factory reset
[Alt+B] nandroid v2.2 backup
[Alt+R] restore latest backup
[Alt+F] repair ext filesystems
-------------------------------
Click to expand...
Click to collapse
And bellow menu there is build ID:
Build: CyanogenMod v1.4 + JF
I don't remember exact procedure that I applied for rooting hero, but I followed instructions from this forum (I can try by searching for exact thread if that may help you).
Edit: I applied root procedure by following instructions on these two links:
http://forum.xda-developers.com/showpost.php?p=4257045
http://forum.xda-developers.com/showthread.php?t=559613
That sounds just perfect
CyanogenMod 1.4 is exactly the same recovery console i have had before.
(Btw, Hero is not officially supported by CM anymore, had a nice discussion yesterday in cyanogen IRC )
So, try to use $su instead of su, that's what I typed and it all worked just great.
But you definitely first booted into bootload and then connected the phone to your pc again?
Tell me if this worked for you, please...
Greetz,
Sven
dinke said:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
Forget about the "su". You are already root.
(You can see this, as there's a '#' in front)
Just do the mounting and flashing
Oh... You're right, nerdture... didn't see the #
I *think* I've tried mount no matter of missing 'su' cmd and it didn't work either but will try again as soon as I manage to find some cable to connect hero with macbook (no longer nearby windows machine but have sdk installed on mac so should be working as well)
Revoluzifer said:
But you definitely first booted into bootload and then connected the phone to your pc again?
Click to expand...
Click to collapse
Yes

[INFO][GUIDE]Rooting on linux (and mac)

There appear to be two main options for rooting Samsung devices on linux and mac.
Option 1: (un-tested) root.zip (recovery)
This method roots your stock 2.3 rom from in recovery (stock or CWM)
1. Copy Root.zip to your sdcard.
2. Turn your phone off
3. Boot your phone into recovery mode. (Hold HOME+POWER buttons. When the screen turns on let go of POWER but keep holding HOME. After you enter recovery mode, let go of HOME.)
4. Select “apply update from sdcard”
5. Find and select Root.zip
6. When it’s done installing, select “reboot system now”
7. Go to apps and look for 'superuser'. If you see it, your phone is rooted.
Option 2: (un-tested) flash CWM from stock recovery:
This gives you the freedom of a custom recovery, flashed on the device from stock recovery
1. Download recovery-clockwork-5.0.2.6-galaxyace-fix.zip
2. Put recovery-clockwork-5.0.2.6-galaxyace-fix.zip on your sdcard
3. Boot into current stock (default) recovery (zip also compatible with CWM recovery)(Hold HOME+POWER buttons. When the screen turns on let go of POWER but keep holding HOME. After you enter recovery mode, let go of HOME.)
4. Go to "apply update from sdcard"
5. Select "recovery-clockwork-5.0.2.6-galaxyace-fix.zip"
6. When it finishes, power off and boot back into recovery mode to check it has installed (it should say "ClockworkMod Recovery v5.0.2.6" somewhere)
Option 3 (un-confirmed): use Heimdall.
An open source, cross-platform, alternative to Odin.
Heimdall is officially supported on the Galaxy S (and S variants including Galaxy Tab)
It allows you to do pretty much anything Odin can do (interact with download mode), and so you can flash a root kernel to gain root and CWM recovery.
Although supposedly untested on the Galaxy Ace, heimdall should be able to flash the usual root precedure (rooting kernel with CWM).
It would be great if someone could verify heimdall works for the Galaxy Ace
Option 4: (un-tested) root your ROM using the zergRush exploit (from the Revolutionary team).
zergRush rooting scripts: Linux, Mac, Windows
For the zergRush exploit scripts, you only root your firmware, so CWM will need to be installed manually afterwards if you want it.
Now that you have root, you should be able to (optionally) flash CWM from an app or over adb using flash_image) (DO YOU NEED ROOT IF THIS IS DONE IN RECOVERY(STOCK)?)
Apps that can flash CWM include:
* CWM Manager
* Flash image GUI
_DO NOT USE_ ROM Manager (reported unstable)
To flash using ADB and flash_image, download flash_image and an CWM recovery img then run:
Code:
cd directory-containing-files/
adb remount
adb push flash_image /system/bin/flash_image
adb shell chmod 0755 /system/bin/flash_image
adb push recovery.img /sdcard/
adb shell
flash_image recovery /sdcard/Recovery.img
rm /sdcard/recovery.img
reboot recovery
Or from the phone's terminal (if BusyBox is installed):
first put recovery.img & flash_image onto /sdcard/
Code:
cd directory-containing-files/
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /sdcard/flash_image /system/bin/flash_image
chmod 0755 /system/bin/flash_image
flash_image recovery /sdcard/Recovery.img
rm /sdcard/recovery.img
reboot recovery
DISCLAIMER: I do not personally own a Samsung phone, and have not yet tested these methods (although I am interested to hear how well they work,and will do my best to update the post). I am however planning to root a friends Galaxy Ace and possibly also an Galaxy S2, so will be testing some of these soon (I'm not sure I should try the untested heimdall on a friends Ace though)
This seems almost utterly pointless, prove me wrong?
Bofu said:
This seems almost utterly pointless, prove me wrong?
Click to expand...
Click to collapse
+1... I don't understand the point.. Why take a longer way when the shorter way is faster, efficient and trustworthy...
ace_viknesh said:
Why take a longer way when the shorter way is faster, efficient and trustworthy...
Click to expand...
Click to collapse
Sorry, which way is this shorter more trustworthy way?
The point of this is listing the methods I believe to be compatible with linux (and by extension mac)
I am new to Samsung phones and do not possess one myself, but understand that using Odin is restricted to Windows.
I will be flashing CWM Recovery to a Galxacy Ace soon and will try methods that have been tested (friend's phone)
If you know of other methods or if one of the listed methods does not work, I will update the post
Also if anyone can confirm heimdall to work with the Ace this would be the first time on xda (searching I've found only people saying it may work) the Ace is not on its supported list, however as it uses the same protocol (right?) it should work?
If however the mods believe this post to be useless or irrelevant, they are welcome to move it to the appropriate location
Point 1- Hopefully useful for Linux and Mac users.
Point 2- If on Windows its much easier and takes very less time..
Also u told about ROM Manager (reported unstable),... Dude leave unstable it bricks our phone... mAking it unusable...
Best way to root is to put the upd.zip in rooting section and flashing in recovery... Can thr be any other way better than that?
Bofu said:
This seems almost utterly pointless, prove me wrong?
Click to expand...
Click to collapse
I use OS X exclusively and this was a very useful post, and at least well written and clear. Most guides blindly assume we all use Windows, not everyone does!!!
For context, owning OS X I originally used the upd1.zip method, flashed via original recovery and it worked, which I suppose is the fastest method you don't cover.
I certainly didn't know about heimdall, great to see an open-source cross platform alternative to odin! Don't need to use it just yet, though testing will be invaluable for future use...
So thanks to the OP for writing clearly about alternative options.
But instaling CWM isn't rooting, you can have CWM without root.
Wysłane z mojego GT-S5830 za pomocą Tapatalk
actually speaking in case of SGA you don't need a PC to root or to anything except heavy logcat
What restrictions using odin on windows are you referring to?
Restriction: it doesn't work if you're not using Windows is the restriction... ;-)
dragonnn said:
But instaling CWM isn't rooting, you can have CWM without root.
Click to expand...
Click to collapse
Thanks, I wasn't sure of this as on my Desire I had to unlock the bootloader (s-off it) due to security features (and this was closely related to the rooting process). I use the term rooting as it seems the most generic, if anyone suggests a better word I will gladly consider changing the title
Prashanthme said:
Also u told about ROM Manager (reported unstable),... Dude leave unstable it bricks our phone... mAking it unusable...
Click to expand...
Click to collapse
I've updated the post advising against using ROM Manager, thanks
Prashanthme said:
Best way to root is to put the upd.zip in rooting section and flashing in recovery... Can thr be any other way better than that?
Click to expand...
Click to collapse
Thank you for this, I will get some details and update the post shortly to include this
Edit: I added the root.zip method
btw, I may rework the post to reflect whether current ROM will be rooted, recovery installed, or both and then list methods for each outcome.
matts95 said:
Thanks, I wasn't sure of this as on my Desire I had to unlock the bootloader (s-off it) due to security features (and this was closely related to the rooting process). I use the term rooting as it seems the most generic, if anyone suggests a better word I will gladly consider changing the title
I've updated the post advising against using ROM Manager, thanks
Thank you for this, I will get some details and update the post shortly to include this
Edit: I added the root.zip method
btw, I may rework the post to reflect whether current ROM will be rooted, recovery installed, or both and then list methods for each outcome.
Click to expand...
Click to collapse
Anyone tested Heimdall yet?

[Q] "Bricked" Allwinner A10 cmp741e Tablet, ADB works but lacks system/bin/sh

[Q] "Bricked" Allwinner A10 cmp741e Tablet, ADB works but lacks system/bin/sh
Hey guys, Please help me out. I am so close to getting the tablet to boot into android OS again but I made a silly mistake and I am not sure what to do now. I am a noob and have tried everything. Your help is greatly and desperately appreciated.
I have the Craig 7" tablet, model CMP741e, processor AllWinner A10.
What happened: I formatted my /system and rebooted, so /system was totally empty. My device will only boot to the splash screen and cannot get to the booting animation. Problem is, there is no hardware key combos to boot into recovery again.
Recovery was installed with this script:
Code:
cat /sdcard/recovery.img > /dev/block/nandg
One could boot into recovery with this script AFTER booting into android OS:
Code:
echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot
I cannot boot into recovery through ADB with the above script because the device does not have /system/bin/sh. Whenever I tried the above command to boot into recovery, it tells me that /system/bin/sh is not found.
I proceeded to adb push the entire /system directory from a nandroid backup into the tablet. HOWEVER, I made a silly mistake of pushing a bogus file named "bin" into the /system directory of the device. Now when I tried to push /system/bin/sh into the device, adb tells me that /system/bin is not a directory ( because there is a file named "bin" within the /system directory of the device).
I tried removing the "bin" file from the /system directory of the device but didn't work. "adb rm" did not work, and "adb shell rm" did not work either because adb tells me again that /system/bin/sh is not found.
For now I am looking for a solution to:
1) boot into recovery again
or
2) delete the "bin" file from the /system directory of the device, so I can push my /system/bin folder into the device.
or
3) anything to get my device to boot into android OS again
Any, any advice would be appreciated. Thank you guys.
why don't you try restoring the firmware by booting off a sdcard as described on the manufacturer page in engrish http://www.craigelectronics.com/site/pdetails.php?id=414
---------- Post added at 03:21 PM ---------- Previous post was at 03:18 PM ----------
were you able to update the os at all? for reference my came out of the box with:
Android cersion 4.0.3
Kernel version 3.0.3+ [email protected] #11
Build number CMP741E_0626_v2.0
i'm gonna try flashing the update and see if its newer or worse
do not flash using stock from craigs website! It will make your unit hang on the Android screen. Looks like the OP figured out how to get his unit back with touch controls based on his post on the androidtablets forrum (search for cmp741e nandroid backup)
I have the same issue, but waiting for him to spell out the steps (seems like a few other people are also waiting on him to respond in that thread).
im in the same boat, i flash the stupid rom on the craig site...ive been able to get cwm on in various stages after flashing another slightly compatible rom using the same dumb phoenix tool but no support for touch so im still trying to figure how to get this **** to work right again and hopefully flash some cm9 or cm10 on it
heres my next try that i hope will work
http://www.androidtablets.net/forum...1e-complete-nandroid-backup-4.html#post269539
have you found a cm that would be compatible with the craig tab? I have been trying to find one and stopped looking as of late
t0mmyr said:
im in the same boat, i flash the stupid rom on the craig site...ive been able to get cwm on in various stages after flashing another slightly compatible rom using the same dumb phoenix tool but no support for touch so im still trying to figure how to get this **** to work right again and hopefully flash some cm9 or cm10 on it
heres my next try that i hope will work
http://www.androidtablets.net/forum...1e-complete-nandroid-backup-4.html#post269539
Click to expand...
Click to collapse
Re: [Q] "Bricked" Allwinner A10 cmp741e Tablet, ADB works but lacks system/bin/sh
I got a cm10 that boots but touch screen doesn't work so I didn't get past the first screen after the boot animation. I can't confirm if anything else didn't work but if I could find a compatibility zip for this device I would cross my fingers that it would work
Sent from my SPH-D710 using xda premium
Have you try to boot from SD card? Not sure if it will work for your devise but you are not loosing anything to try...
http://forum.xda-developers.com/showthread.php?t=1605664
Craig CMP741e is stuck in boot loop on the Android logo.
When I try to install or mount using adb cmd I get read only errors and I have tried almost everything to recover/reset the tablet. i opened it unplugged it, tried reset pinhole, hold vol+ power buttons, and phonixcard does not work.
I am able to get this tablet recognized with using the Android SDK bundle, but I do not how to use it really...I appreciate some help on how to do a hard reset or factory reset. i hear theres no key combo for this...i recorded whats going on inside during start up using andriod debug monitor... can i use that to somehow fix it?
delete the spaces in link.. its legit no spam its my problem i need a solution too, plz help
. you tube. com/ watch? v= Rcy kDInH sYE

Looking for cwm and custom rom for an rk2928 device

Good morning,
i recently bougth a nordmende nd-101 tablet.
It mounts a Rk2928,i successfully rooted it but i'm not able to install cwm.
Can anyone help me please to find properly cwm and custom rom for this device?
Here is an info screenshot.
Thanks in advance.
patria o muerte said:
Good morning,
i recently bougth a nordmende nd-101 tablet.
It mounts a Rk2928,i successfully rooted it but i'm not able to install cwm.
Can anyone help me please to find properly cwm and custom rom for this device?
Here is an info screenshot.
Thanks in advance.
Click to expand...
Click to collapse
Hello! I have also rk2928
Download rk generic zip from here
http://androtab.info/clockworkmod/rockchip/rk2928/
And then unzip it using root browser and then move flash_image and recovery.img to
/dev
And then install terminal emulator from play store and run it
Then type su
Then : chmod 755 /dev/flash_image (enter)
/dev/flash_image recovery /dev/recovery.img ( enter)
Then enjoy
Hit thanks if i helped.....
RIP Emerson EM744
karan luniyal said:
Hello! I have also rk2928
Download rk generic zip from here
http://androtab.info/clockworkmod/rockchip/rk2928/
And then unzip it using root browser and then move flash_image and recovery.img to
/dev
And then install terminal emulator from play store and run it
Then type su
Then : chmod 755 /dev/flash_image (enter)
/dev/flash_image recovery /dev/recovery.img ( enter)
Then enjoy
Hit thanks if i helped.....
Click to expand...
Click to collapse
After doing this I went to boot into recovery but it wont turn on. I wonder if tearing it apart and doing a battery pull will do anything or is it a paperweight now?
Those RKxx generic recoveries do not really work generic on all Rockchip devices. I got the same issues with a RK3066 based Tablet.
its not really bricked. Just switch back to regular recovery by flashing a complete ROM image and the device should start again.
It's working again. After sitting for a day it starts. I was trying to put recovery on there so I could install play. It belongs to a friends little kid so that's why I'm messing with this turd.
Can't blame him for giving a little kid a black Friday special. You don't give a little kid a Nexus 7 abuse.
Sent from my LS970 using my thumb
Jubeldum said:
After doing this I went to boot into recovery but it wont turn on. I wonder if tearing it apart and doing a battery pull will do anything or is it a paperweight now?
Click to expand...
Click to collapse
retry man by using adb shell (pc)
btw it happened with me but i tried again cwm and it worked...

[F5122] Can TWRP recovery in POISON works on Android 6.0.x?

Hi guys. I am new to xda and I still cannnot post on the original thread posted by @lubik1 :
https://forum.xda-developers.com/xperia-x/development/romubxperia-poison-v1-0-xx-f5121-5122-t3525884
I rely on xposed very much so I still do not wanna flash Nougat now.
So I come out with a simply question that can the recovery in POISON post works fine on Android 6.0.x?
I want to flash xposed into my F5122.
BTW i flashed xposed by flashfire for many times but failed (black screen). I installed xposed with xposed installer but it cased bootloop.
It's driving me carzy.
I just want to root my phone, install twrp recovery (for future flashing) and xposed. Can anyone help me?
Thx a lot!
yujincheng08 said:
Hi guys. I am new to xda and I still cannnot post on the original thread posted by @lubik1 :
https://forum.xda-developers.com/xperia-x/development/romubxperia-poison-v1-0-xx-f5121-5122-t3525884
I rely on xposed very much so I still do not wanna flash Nougat now.
So I come out with a simply question that can the recovery in POISON post works fine on Android 6.0.x?
I want to flash xposed into my F5122.
BTW i flashed xposed by flashfire for many times but failed (black screen). I installed xposed with xposed installer but it cased bootloop.
It's driving me carzy.
I just want to root my phone, install twrp recovery (for future flashing) and xposed. Can anyone help me?
Thx a lot!
Click to expand...
Click to collapse
I haven't tried putting xposed on mine as of yet but its took me a while to actually get it all sorted with nougat on my device.
I hot booted the recovery through flashtool instead which worked fine use this one i have uploaded https://drive.google.com/open?id=0B2iNRglthTH2a1JuZWlxaGFkTDQ
obviously make sure you have the rom file on your phone and supersu.zip file too for when you are flashing in recovery and dont forget to give the phone a wipe in recovery first.
Any problems give me a shout ill see what i can do.
TWRP recovery in a xperia x F5121
Hello again, I am trying to install the TWRP recovery in a xperia x F5121, but when I reboot the screen is black and I can not start in any way ... does anyone know which version is correct and how to install it correctly?
Thanks in advance
yujincheng08 said:
BTW i flashed xposed by flashfire for many times but failed (black screen). I installed xposed with xposed installer but it cased bootloop.
It's driving me carzy.
I just want to root my phone, install twrp recovery (for future flashing) and xposed. Can anyone help me?
Click to expand...
Click to collapse
I've installed Xposed on my phone without using any recovery. This is what I did following serajr instructions https://forum.xda-developers.com/showpost.php?p=69993876&postcount=87 and using adb from a computer
Code:
adb shell
& su
# mount -o remount,rw /system
# busybox unzip /sdcard/xposed-v87-sdk23-arm64.zip META-INF/com/google/android/update-binary -d /tmp/
# chmod 777 /tmp/META-INF/com/google/android/update-binary
# /tmp/META-INF/com/google/android/update-binary 3 0 /sdcard/xposed-v87-sdk23-arm64.zip
# reboot
Be sure you to have a modified kernel for your phone version (something like this kernel https://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708, or you can make you own modded kernel) and the Xposed zip in /sdcard folder. And remember that for now Xposed in the Xperia X only works in MM.
juliompinheiro said:
I've installed Xposed on my phone without using any recovery. This is what I did following serajr instructions https://forum.xda-developers.com/showpost.php?p=69993876&postcount=87 and using adb from a computer
Code:
adb shell
& su
# mount -o remount,rw /system
# busybox unzip /sdcard/xposed-v87-sdk23-arm64.zip META-INF/com/google/android/update-binary -d /tmp/
# chmod 777 /tmp/META-INF/com/google/android/update-binary
# /tmp/META-INF/com/google/android/update-binary 3 0 /sdcard/xposed-v87-sdk23-arm64.zip
# reboot
Be sure you to have a modified kernel for your phone version (something like this kernel https://forum.xda-developers.com/xperia-x/development/root-xperia-x-34-0-2-292-modified-t3449708, or you can make you own modded kernel) and the Xposed zip in /sdcard folder. And remember that for now Xposed in the Xperia X only works in MM.
Click to expand...
Click to collapse
Thx a lot!
I have tried this before but I put xposed zip into boot.img then failed.
I think it's the xposed in boot.img and the one I flash into my phone by flashfire conflict.
I will have a try on your method. Thx again!
BTW I have a problem to ask you how to make selinux permissive? Does the lucky patcher work well?

Categories

Resources