Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Dexter885 said:
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Click to expand...
Click to collapse
Look here: http://forum.xda-developers.com/showthread.php?t=2439949.
It seems that the bootloader is locked.
tylerr55 said:
Look here: http://forum.xda-developers.com/showthread.php?t=2439949.
It seems that the bootloader is locked.
Click to expand...
Click to collapse
If overwriting / dev/block/mmcblk0p5 with emmc_appsboot.bin, the phone will not boot up. It must be restored with an image kdz.
Any news? I've been waiting for cwm for long
Hey,
The correct comand on adb to unlock bootloader on Lg devices is:
adb reboot oem-unlock
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
reffer to http://forum.xda-developers.com/showthread.php?t=2224020
pedrocel85 said:
Hey,
The correct comand on adb to unlock bootloader on Lg devices is:
adb reboot oem-unlock
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
reffer to http://forum.xda-developers.com/showthread.php?t=2224020
Click to expand...
Click to collapse
Someone try this method on P710?
try, it will do no harm
maxx_hr said:
Someone try this method on P710?
Click to expand...
Click to collapse
Did you try it?
Did it work?
======================
OP:
Dexter885 said:
Hello to all
I'm trying to porting cyanogenmod, but I have a problem unlocking the bootloader for recovery. Let me explain what I've done so far.
Root Phone via framaroot
Extracts recovery.img boot.img via adb
Code:
sudo adb start-server
adb shell
su
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
exit
exit
adb pull /sdcard/booty.img
adb pull /sdcard/recovery.img
Initialized the project via mkvendor.sh
Code:
mkdir ~/android/system/vendor/LGE/vee7e
mkdir ~/android/system/device/LGE/vee7e
~/android/system/build/tools/device/mkvendor.sh LGE vee7e ~/boot.img
cd ~/android/system/
. build/envsetup.sh
make -j4 revoveryimage
make -j4 recoveryzip
I now have the CWM Recovery, and I inserted in my phone
Code:
cd ~/android/system/out/target/product/vee7e/
adb push recovery.img /sdcard/recovery-cwm.img
adb shell
su
dd if=/sdcard/recovery-cwm.img of=/dev/block/mmcblk0p17
Reboot the phone for enter in recovery mode (hold volume up + home button), and I had this surprise
Code:
[4380] -------------------------------------------------------------------
[4380]
[4380] Secure booting Error!
[4390] Cause: boot certification verify
[4390]
[4390] -------------------------------------------------------------------
Is there anyone who can help me?
Thanks
P.S. In the attached you will find my recovery and the error message.
P.P.S. Sorry for my bad English
Click to expand...
Click to collapse
Any news about the recovery?
Vagelis1608 said:
Did you try it?
Did it work?
======================
OP:
Any news about the recovery?
Click to expand...
Click to collapse
Tried, does not work!, Googling I found this guide,
Code:
://translate.googleusercontent.com/translate_c?depth=1&hl=it&rurl=translate.google.it&sl=ru&tl=en&u=http://4pda.ru/forum/index.php%3Fshowtopic%3D466295%26st%3D0&usg=ALkJrhhM8yja33NUhK__pNP0aLRznOSGhg#entry22312158
But it not work well on the P710. I found this bug: when you disconnect and reconnect the battery the phone will not turn over and go into an infinite loop!
Necessary to crack the bootloader, but I nn I know these ...
The cwm start on my lg p710 but the same problem with battery,if i go in cwm(volum down+home+power)and rebot from there the phone start.
Sorry for my bad english.
I try CWM from this thread:
http://forum.xda-developers.com/show...2700579&page=3
on my P710, and it works-no upside down problem, no bootloops.
But I dont install gscript, just put APPSSBL.bin and recovery.img on their places.
After that, i perform backup with one warning message-no file_contexts, but on second backup it dissapears...:good:
nobody here still unlocked L7 II bootloader ?
please take look at this
http://forum.xda-developers.com/showthread.php?t=2212092&page=4
since page 4 there are users talking about unlocking bootloader and it seems some of them did unlock bootloader and installed succesfully CWM.
RenatoNismo said:
nobody here still unlocked L7 II bootloader ?
please take look at this
http://forum.xda-developers.com/showthread.php?t=2212092&page=4
since page 4 there are users talking about unlocking bootloader and it seems some of them did unlock bootloader and installed succesfully CWM.
Click to expand...
Click to collapse
Just see link from my post, this is newer version of your, taken from same russian site.
With this bootloader and CWM, i just flash some P713 mod (deodexed, with kit-kat look), but i can confirm some problem with restoring-everything works, but restoring data (maby because i have more than 500 files in one folder ) failed. I must try restoring without that amount of data.
Anyway, backup in my case, is success, because restoration of sistem/boot gives me result like factory reset of original (but some data, before error is restored). After restoring, i just reset/clean dalvik to clean garbage, and phone works like new one, and even stay rooted.
Sorry for bad english...
Related
I can't seem to get the custom recover working on my eris. I followed the "adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.img
4. Close the command prompt and turn off you phone."
to the tee and everything seemed to work.I didnt recieve any error msg on the cmd console but when I boot up holding the Vol+ and power I get and Android under a ! in a triangle and a message that says "E:Can't open /cache/recovery/command then I only get 4 options and none of them are to flash a rom so I always reboot system. I really want to put a rom on here but I have no idea what went wrong. Im sorry if this is a redundant post. I combed a hundred of them and couldnt find anything like this. Thank you for any help in advance.
Oh and before I forget I tried the adb fastboot bootloader version as well. Everytime I do it it sits in the command console stating "waiting for device". Im plugged in so I dont understand what Im doing wrong.
Curious to know... are you using windows or mac? have you tried:
adb shell reboot recovery
to see if that does anything?
Maybe you have a different version of the recovery saved than I do, but mine is named "recovery-RA-eris-v1.6.2.img"...maybe you just had an input error somewhere along the line? forgot a capital letter or something? I had the same error myself and following the directions I got the recovery image back
Im running windows 7 and I have both recovery-RA-eris-v1.6.2.img and the recovery-RA-eris.img. I have been using the v1.6.2 and I just modify the command to look like this "adb push recovery-ra-eris-v1.6.2.img /sdcard" How would I use adb shell reboot recovery would I just sub that in place of something? kinda getting discouraged because I have tried this 10x now. I have checked and the usb debugging is on and I do have the eris 2.1 root and not the leak. I wonder is there any way I can flash this with something from the droid mkt place like SUFBS? Or maybe change a rom's name to look like an update zip?Just looking for ways to make this work Im so jealous of everyone that has got it to work.
here is another question and it might be that this is why its not working with the fastboot option but on this website's walk through thefuzz4.net it states to "You will have FASTBOOT highlighted in red like it is here" Now Im not a pro at this but what does this mean? How do I highlight text in the command shell? I would post the full url but since Im new it wont let me post urls yet.
Dachix said:
here is another question and it might be that this is why its not working with the fastboot option but on this website's walk through thefuzz4.net it states to "You will have FASTBOOT highlighted in red like it is here" Now Im not a pro at this but what does this mean? How do I highlight text in the command shell? I would post the full url but since Im new it wont let me post urls yet.
Click to expand...
Click to collapse
when hes saying fastboot will be highlighted in red he's referring to booting your phone into the standard recovery mode (when power is off) hold volume up and power.
Walking Taco seriously love that name. The only options I get when I hold down vol+ and pwr is 1. reboot system now 2. apply sdcard update 3. Wipe Data/ factory reset 4. Wipe cache partition and all are in purple and at the bottom on the phones screen is "E:Can't open/cache/recovery/command"
The website fuzz4net says to:
WINDOWS USERS
From your tools directory in the sdk do the following command
adb fastboot bootloader
You will have FASTBOOT highlighted in red like it is here
Now on your computer do the following
Fastboot flash recovery recovery-RA-eris-v1.6.2.img
Ok after that completes pull the battery then power back up with Vol Up + Power to enter recovery
But when I get done ...after the last step the cmd.exe window states <waiting for device> any ideas? Thanks for helping too. Leave it to me to hit a snare
almost forgot when it gets to <waiting for device> nothing happens I literally have left and come back 3 hours later and no progress was made
Dachix said:
almost forgot when it gets to <waiting for device> nothing happens I literally have left and come back 3 hours later and no progress was made
Click to expand...
Click to collapse
I honestly don't know man, I would factory wipe it and try and start from the beginning. I followed the fuzz's instructions and was rooted in less than a half hour. Sorry brother.
Thanks!
ROOTED!!!!!! Here is what I did:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.v1.6.2.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.v1.6.2.img
This was not working until I deleted the spaces in between img/sdcard for all the commands. Then and I do not know why but when I would turn odd my phone the vol+ pwr on it would not work so instead I used the adb shell reboot recovery command like droidfreak suggested then BOOYAH the custom recovery was loaded thank you all for helping me.
Dachix said:
ROOTED!!!!!! Here is what I did:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery-ra-eris.v1.6.2.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery-ra-eris.v1.6.2.img
This was not working until I deleted the spaces in between img/sdcard for all the commands. Then and I do not know why but when I would turn odd my phone the vol+ pwr on it would not work so instead I used the adb shell reboot recovery command like droidfreak suggested then BOOYAH the custom recovery was loaded thank you all for helping me.
Click to expand...
Click to collapse
Awesome news! Have fun with your rooted phone!
Hi Guys.
I don't know if this is the right forum, please tell me if so.
I think that I've screwed up bigtime when i tired to upgrade my recovery image. Here is what happende.
I have rooted my Hero a long time ago, so what i did was trying to follow this guide for installing the latest recovery image: http://forum.xda-developers.com/showthread.php?t=645253
when i tired to flash the recovery image using this command: flash_image recovery /sdcard/recovery.img. I was using Terminal Emulator.
What happened was i got a lot of error messages saying that the phone was out of memory. This resulted in that i couldn't get acces to the recovery menu when rebooting my phone and that i cant access my phone rom.
I then tired to flash the recovery image using the installation guide of this thread: http://forum.xda-developers.com/showthread.php?t=561124
The thing is that i can see that the phone is mounted through the "fastboot devices" commando
When i try to flash the recovery image using fastboot i get this error message:
C:\android-sdk-windows\tools>fastboot boot recovery.img
downloading 'boot.img'... FAILED (remote: not allow)
finished. total time: 0.001s
HELP! What can i do? Is my hero 'saveable or is it bricked?
//Mads
First of all its not bricked don't worry. Do you still have old recovery of Amon_Ra or not ? If have than put latest version of Amon_Ra recovery into your sdcard & reboot your phone into old recovery of Amon_Ra Than just follow these commands
Code:
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
when its done just type adb reboot . your phone will reboot
Hope it helps
Hi, it's good to hear. I think that my old recovery mode was screwed up during the attempt to upgrade. because if i tries to boot into it it just stops at the HERO bootscreen and goes no futher. If i just try to boot normally it goes to a black screen and then nothing else happens. Tried to let it boot for 30 min without anything happening.
The only thing i can access is fastboot.
when i try adb shell it says the following:"
C:\android-sdk-windows\tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
you need to update your drivers that means you are not having latest drivers .. there was a thread i guess download drivers & check how to set up correct adb drivers on windows .. & by the way do you have installed HTC Sync ? make sure you have installed HTC Sync because it finds all htc drivers i guess than try
Code:
adb shell reboot bootloader
fastboot boot recovery-RA-hero-v1.7.0.1.img
adb shell mount /sdcard
adb push recovery-RA-hero-v1.7.0.1.img /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
adb shell reboot
Thx for the help, but that didn't work either.
I found this guide http://forum.xda-developers.com/showthread.php?t=714519 which did the work. So now i'm back at 1.5 for a little while, just need to root right away The good thing is that my phone is working
Thx for the help.
Glad to hear it Men .. Well come abroad
I am sitting here the whole Day....
i read so much threats about to root this Tablet, but nothing works.
my English is not the best so i have problems to explain whats the Problem
I have SDK, i have adb, i have all the drivers..... the tab is known when its normal on, and also when its in bootloader...
if i make the cmd: adb devices.... he tell me the name of the tablet, but not the IMEI, is that a problem???
if i tell him: fastboot boot superboot.img.... he download the boot.img... boot okay.... but nothing else....
there is no superuser in the system folder.. because there is no system folder....
i dont know what i should do....
and when i try to unlook : fastboot oem unlock..... he just say he is waiting for device....
i sit here since 9 o-clock in the morning... and i get crazy...
please.... help me....
nobody could help me????
yesterday i could do something more....:
-> Write the following commands withing the command line:
--> adb reboot bootloader
--> fastboot boot superboot.img
--> The device should now boot with the Superuser.apk installed and SU in the /system/xbin/su, as well as allowing you adb root commands. Now run the following:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
after adb shell..... there comes a # at the beginning, and than i wright ne In -s /system xxxxxxxxxxxxx
but then he say... could find In:
superuser is on the tablet, but i think only the thing with the files should be done, without it i can do nothing....
what could i do?????????
if nobody knows whar V71A is... Vodafone Smarttab 7
http://forum.xda-developers.com/showthread.php?t=1473555
Im starting this new thread because I was not able to find a solution for my problem for about 2 weeks now.
Issue : Unable to install recovery. Im trying to install recovery by following this thread : http://forum.xda-developers.com/showthread.php?t=2221102 - in the 3rd step when i flash the recovery i get this error "command write failed - unknown error"
- tried almost all the different types of steps available in xda and also outside xda.
My Environment:
Win8 Pro 32bit
LG optimus L9 flashed and rooted by lelus method - Current ROM - P76020c
Installed all LG drivers - PC suite is installed
Have SDK manager installed
Device is recognized when I run the "adb devices" command keeping phone switched on.
Device is recognized when I run the "fastboot devices" command when phone is in fastboot mode.
So I guess this is not a driver issue.
Im also attaching screenshots of the error and the commands that I have ran ....
SOOOOOOOOOOOO ... whats the prob here .... ... anyone faced this same prob ???? HELPPPP
rkn989 said:
Im starting this new thread because I was not able to find a solution for my problem for about 2 weeks now.
Issue : Unable to install recovery. Im trying to install recovery by following this thread : http://forum.xda-developers.com/showthread.php?t=2221102 - in the 3rd step when i flash the recovery i get this error "command write failed - unknown error"
- tried almost all the different types of steps available in xda and also outside xda.
My Environment:
Win8 Pro 32bit
LG optimus L9 flashed and rooted by lelus method - Current ROM - P76020c
Installed all LG drivers - PC suite is installed
Have SDK manager installed
Device is recognized when I run the "adb devices" command keeping phone switched on.
Device is recognized when I run the "fastboot devices" command when phone is in fastboot mode.
So I guess this is not a driver issue.
Im also attaching screenshots of the error and the commands that I have ran ....
SOOOOOOOOOOOO ... whats the prob here .... ... anyone faced this same prob ???? HELPPPP
Click to expand...
Click to collapse
As always, use at your own risk.
Upload recovery image to sdcard and change the file name to recovery.img if that helps
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
or terminal emulator straight from the phone
Code:
su
busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
Lelus said:
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
[/QUOTE]
is this the exact code that we should type into the cmd after getting to fastboot mode ??? or shud this be ran while phone is switched on ???
Click to expand...
Click to collapse
rkn989 said:
is this the exact code that we should type into the cmd after getting to fastboot mode ??? or shud this be ran while phone is switched on ???
Click to expand...
Click to collapse
phone switched on, usb mode: camera or lg software
btw, you have unlocked the bootloader , right ?
Lelus said:
phone switched on, usb mode: camera or lg software
btw, you have unlocked the bootloader , right ?
Click to expand...
Click to collapse
yess .... my bootloader is unlocked ....
tried this and get an error - su not found - check screenshot
im not getting the command that we tried :
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
"su" stands for ???
and where should i copy the .img file to ?? (i copied it to the root of the ext sd card)
anyone any suggestions ?????
May be your file is corrupt. Just give it a try.
Download latest version of CWM Touch and Non-touch version from http://www.clockworkmod.com/rommanager and try again.
cmahendra said:
May be your file is corrupt. Just give it a try.
Download latest version of CWM Touch and Non-touch version from http://www.clockworkmod.com/rommanager and try again.
Click to expand...
Click to collapse
Ive already tried that ... have tried downloading the files many times .. already have 4-5 copies of both the normal and touch recoveries ...
Its the same error !!!!!!
And yu want me to try by the fastboot method rite ?? not the method lelus juzz said ???
Lelus said:
flash via adb from your computer
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
or terminal emulator straight from the phone
Code:
su
busybox dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p4
Click to expand...
Click to collapse
Can yu explain this in more detail. ????
Sent from my LG-P760 using xda app-developers app
rkn989 said:
Ive already tried that ... have tried downloading the files many times .. already have 4-5 copies of both the normal and touch recoveries ...
Its the same error !!!!!!
And yu want me to try by the fastboot method rite ?? not the method lelus juzz said ???
Click to expand...
Click to collapse
Lelus is explaining you in details and he is expert here. I am just confirming that if you have tried the basic things or not. By the way, your fastboot drivers seem working as device responds to "fastboot devices" command properly.
The fastboot screen should show the phone is unlocked or not, exactly like this....does it show like this screenshot?
SW Upgrade mode also should show unlocked like this screnshot.
If not, you may not be yet Unlocked and fastboot will not work.
cmahendra said:
Lelus is explaining you in details and he is expert here. I am just confirming that if you have tried the basic things or not. By the way, your fastboot drivers seem working as device responds to "fastboot devices" command properly.
The fastboot screen should show the phone is unlocked or not, exactly like this....does it show like this screenshot?
SW Upgrade mode also should show unlocked like this screnshot.
If not, you may not be yet Unlocked and fastboot will not work.
Click to expand...
Click to collapse
I din know where exactly to run those commands, so asked detailed steps
And the my bootloader is unlocked, I get the fastboot boot mode when I run the adb reboot command to unlock bootloader, yday when I flashed my phone with v20c, I gt the second screenshot as yu mentioned, also i tried running that *# command from inside the phone and it showed bootloader status- unlock.
So I hope it is unlocked! !!
Sent from my LG-P760 using xda app-developers app
ATLASTTT !!!!!!!!!!!!! I have succeeded in flashing my recovery .....
but the resolution is strange .... it just worked fine in WIN7 .... isn't that strange ???????????
I have a chinese Allwinner 7" tablet ( Rocky M713HD ) , I was trying install a CWM recovery image. I connected my tablet to PC, opened my terminal and taped:
adb push recovery.img /data/
adb shell "cat /data/recovery.img > /dev/block/nandg; sync"
adb shell "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot"
After that, my tablet freezes on bootloader with no single info on adb when typing "adb devices"
As you can see, I missed a caracter on the 3rd line: ( nandg/nandf )
Can anyone give me a solution to flash my tablet? I was on Allwinner 4.2.2 ROM.
Thank you in advance!
Was your bootloader unlocked prior to flashing recovery?
Rudjgaard said:
Was your bootloader unlocked prior to flashing recovery?
Click to expand...
Click to collapse
No
Then that's most likely your problem.
You should restore stock fw and then start from scratch remembering to unlock bootloader this time
(or you can use cwm app from playstore i think it can install recovery on locked bl)
can u go to download mode
ummarrkhan said:
can u go to download mode
Click to expand...
Click to collapse
No, now, it's only showing me the manufacturer's logo. I only have Power and Home buttons, I tried some combinations but nothing happened
elacheche.bedis said:
No, now, it's only showing me the manufacturer's logo. I only have Power and Home buttons, I tried some combinations but nothing happened
Click to expand...
Click to collapse
bring to service center